|
PureBytes Links
Trading Reference Links
|
It was first mentioned in release notes for AB 4.88. also
quoting from another message:
> -----Original Message-----
> From: AmiBroker-at@xxxxxxxxxxxxxxx On Behalf Of Tomasz
Janeczko
> Sent: Friday, October 20, 2006 12:32 PM
> To: AmiBroker-at@xxxxxxxxxxxxxxx
> Subject: Re: [AmiBroker-at] Re: Conditional #include
>
> Hello,
>
> I took a look at code part that handles comments and
improved
> it now, so single line of /* */ comment takes now 0.14
microseconds,
> when single line of // comment takes 0.10 microseconds.
>
> Best regards,
> Tomasz Janeczko
> amibroker.com
I am glad I bothered searching for the original information.
I somehow remembered the numbers were in milliseconds not
microseconds. Ok, I will be able to sleep better now ;)
Joseph Biran
____________________________________________
-----Original Message-----
From: amibroker@xxxxxxxxxxxxxxx
[mailto:amibroker@xxxxxxxxxxxxxxx] On Behalf Of tuzo_wilson
Sent: Tuesday, August 05, 2008 10:44 AM
To: amibroker@xxxxxxxxxxxxxxx
Subject: [amibroker] Re: AFL programming style questions
--- In amibroker@xxxxxxxxxxxxxxx, "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
------------------------------------
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
For other support material please check also:
http://www.amibroker.com/support.html
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/amibroker/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:amibroker-digest@xxxxxxxxxxxxxxx
mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx
<*> To unsubscribe from this group, send an email to:
amibroker-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|