--- In amibroker@xxxxxxxxxps.com,
"J. Biran" <jbiran@xxx> wrote:
>
> Well, as you can tell, I am for solution 1. If afl can keep
> track of parentheses I see no reason why it cannot do the
> same for /* */.
You're right -- it can be done but I can think of a couple of reasons
why it shouldn't be done.
Standards: AFL's C style (/* */) comment behavior is standard
throughout many programming languages (C, C++, C# Java). In most
languages, C++ style comments (//) are preferred over the older C
style comments.
Logical: When text is commented out (i.e. placed between "/*" and
"*/") it makes sense that the parser ignore any characters until the
matching end comment is found. I, for one, don't want to be editing
the syntax of comments to match up "/*" & "*/".
With that said, the potential to nest comments during debugging is a
pain and that is why C++ style (//) comments are usually preferred.
I think that a comment/uncomment option within the AFL editor would be
a nice to have.
Lastly, what exactly is the performance penalty for C++ style comments
in AFL (as opposed to C style comments)?
Tuzo