Coloring "return" and type parameter Follow

How to about coloring "return" keyword in customizable way?

>

I think this is very important to see such control flow in the member
for reading, refactoring, rewriting code.

Hmm...

And "break" and "continue" in loops too (one color for 3 things), this is
all
the normal control flow.

Hello Vladimir,

how about 'throw', it also disrupts normal control flow.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> How to about coloring "return" keyword in customizable way?
>>
>> I think this is very important to see such control flow in the member
>> for reading, refactoring, rewriting code.
>>

Hmm...

And "break" and "continue" in loops too (one color for 3 things), this
is
all
the normal control flow.

how about 'throw', it also disrupts normal control flow.

No, it's about abnormal control flow, it's not expected in general cases.
And there is no posibility to get off from it, but there is posibility often
to
rewrite code without some "return", "continue" and "break" (in loops).

>> how about 'throw', it also disrupts normal control flow.
>

No, it's about abnormal control flow, it's not expected in general cases.
And there is no posibility to get off from it, but there is posibility
often to rewrite code without some "return", "continue" and "break" (in
loops).

Yes, i'm talking about control flow that you can redesign (that can
be implemented in different ways) - return, continue and break (in
loops), and goto also (in switch too i think). But not break in
switch (break in switch is redundant language element).

I think it's a good idea to show a different colour for the exit points or
have some option that exit points can be visually marked with for example a
highlighted line or something else

Gabriel Lozano-Morán

"Vladimir" <none@none.none> wrote in message
news:e59dbv$oe0$1@is.intellij.net...
>>> how about 'throw', it also disrupts normal control flow.
>>
>> No, it's about abnormal control flow, it's not expected in general cases.
>> And there is no posibility to get off from it, but there is posibility
>> often to rewrite code without some "return", "continue" and "break" (in
>> loops).
>

Yes, i'm talking about control flow that you can redesign (that can
be implemented in different ways) - return, continue and break (in
loops), and goto also (in switch too i think). But not break in
switch (break in switch is redundant language element).

>
>

I've just released a plugin the highlights the keywords :return
,throw,continue,break and goto.

You can check it in the jetbrains.resharper.openapi newsgroup.

Ran Wakshlak