News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Indent on comment with indent lines afterwards?

Started by AraspiK, April 02, 2017, 10:08:31 PM

Previous topic - Next topic

AraspiK

* MISLEADING SUBJECT * I had no idea how to put this in words
Sometimes my code goes:
// LOCAL INCLUDES
    #include "..."
// SYSTEM INCLUDES
    #include <...>

Or:
class myClass {
    string var1
    // Lambdas
        std::function<void(void)> func

    public:
        ...
}

How can I tell C::B to fold the indent stuff after a comment and keep such formatting? VSCode supports this, if anybody wants to know.
PS: My code: https://github.com/AravK/KGB2

oBFusCATed

Can you please try to explain your problem with more details. I have no idea what you're trying and what it doesn't work.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

AraspiK

I want
// foo
    string bar;
    foobar fooBar;

to become
// foo ...

ollydbg

Quote from: AraspiK on April 03, 2017, 05:51:39 PM
I want
// foo
    string bar;
    foobar fooBar;

to become
// foo ...
I still don't understand what's the problem you have. Can you give more details? What is the current/exprect way, what is the steps to reproduce this error.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

blauzahn

sounds like he wants code-regions like in C# where you can fold away all the crappy stuff under the rug.

Whether that is a good technique is IMHO debatable. If you feel it being necessary when
dealing with big classes it may be time to think about splitting it because it probably plays
more than one role.

BlueHazzard

#5
You can add
//{
This can be folded
//}


to your comments and you will be able to fold this

for example:

// LOCAL INCLUDES
//{
    #include "..."
//}
// SYSTEM INCLUDES
//{
    #include <...>
//}


There is now easy way to make this generic... How should a parser know where to start folding and where to stop?