labels inside the code #pragma mark label

Hi everyone
I am mac OS programmer, with some C programming experience and no much windows programming experience.
I wonder if there is and kind of equivalent to
#pragma mark My_label
where My_label is the name for a label inside the code and recognized by tools like Xcode. (and as far I know some linux tools also does recognize #pragma mark)
In this case, I want my label be recognized by Visual C++ 2008 but #pragma mark label is not working. I suppose there is a different way wich I don't know. :(
Please see attached JPG file.

Help Please... My code is getting bigger and bigger and the is kind of difficult to see line by line.

Thanks in advances.

There is no such functionality to my knowledge. Why do you need a label? It clearly outlines all your functions.
And if you need to group them, you can always put them into other files.
So what exactly is the problem?

Pragmas, as a rule, are compiler-specific. Visual Studio doesn't know the mark pragma.

It might recognize the region pragma. It was introduced in C#, but it might have been ported.

to Elysia: I need labels because my functions are too complicated and long. (in the picture is just a simple program but, )I have to manage with 2 or 3 solutions, wich have alike content. So a Label would solve all my problems. ;)

to CornedBee: Can you explain more about the region pragma please ;)
is it something like #region pragma maybe?

thanks.

CornedBee, I just took a look, and I think #pragma region would work great for grouping code (in regions as the name suggest) but I t does not appear in the "global scope" place (the place where al my functions and types are listed.)

#pragma region label
...
content
...
#pragma endregion

it seems to be like Elysia said... there is no such a functionality!. BUUUU!!! VC++ :(

Quote:

---

Originally Posted by nacho4d

I need labels because my functions are too complicated and long.

---

Then there are several things you should do:
1) break up large functions into smaller ones, such that each function does exactly one thing.
2) Use object oriented design to group your functions and the data they deal with into classes.
3) Use namespaces to group related functions.

You can refer to documentation if the purposes of the functions are unclear. Tools like doxygen can generate documentation from the source.