2 Ide Features

[Psychophanta]

Logical because of knowing the internal working way, then yes, the behaviour is logical.
But not so logical for a programmers point of view, imho.

[freak]

Why ?

Inside a Compilerif, everything is ignored. Including macros.
You need no internal knowledge to understand that.

Macros are also not expanded inside comments as well, and nobody would think that
to be illogical either.

[Psychophanta]

Inside a Compilerif, everything is ignored. Including macros.

I see now. Sorry, Thanks.

[PB]

>> Which sucks to do when the block is more than a screen size long
>
> That would be a lot of comments

Yes. Sometimes I need to disable a procedure, and when the procedure is
several screen lines long (such as SendKeys), then it becomes a hassle to
select it all and then press CTRL+B.

Also, Freak's CompilerIf solution (which I also once posted) works, but none
of the "commented" code appears in the comment color, which isn't good.
It still looks like uncommented code if you scroll through your source.

[Thalius]

Yes. Sometimes I need to disable a procedure, and when the procedure is
several screen lines long (such as SendKeys), then it becomes a hassle to
select it all and then press CTRL+B.

I usually disable functions if needed with a Macro:

Code: Select all

Procedure a(b)
  ; do something
  PrintN(Str(b))
EndProcedure

Macro a(b) : EndMacro ; Disable Function a()

Thalius

[#NULL]

i make use of folding sequences (like with ";{-") quite a lot, so if i want to uncomment a (bigger) sequence, i just unfold it and can mark it easily on 3 lines.

[netmaestro]

It's a neat trick but the syntax coloring and keyword recognition happen inside the block, making it too irritating to be a real solution. Turning that off for CompilerIf blocks would make a mess, so some actual comment block keywords would be a nice addition. (just noticed that PB made the same observation, so I agree with him)

[Derek]

Yes. Sometimes I need to disable a procedure, and when the procedure is
several screen lines long (such as SendKeys), then it becomes a hassle to
select it all and then press CTRL+B.

I just chuck in an extra character in the name of the procedure and put a new empty definition in front of the old one.

Code: Select all

Procedure P1()
..
..
EndProcedure

becomes

Code: Select all

Procedure P1()
EndProcedure

Procedure oP1()
..
..
EndProcedure

Not the most elegant way of doing things but it saves scrolling through screens of code to ctrl+b.