s measurement was done long time ago and on your
> modern computers
> timings should be ~5 times less.
>
> Best regards,
> Tomasz Janeczko
> amibroker.com
> - Original Message -
> From: "Dennis Brown" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesda
.
Best regards,
Tomasz Janeczko
amibroker.com
- Original Message -
From: "Dennis Brown" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, August 05, 2008 9:44 PM
Subject: Re: [amibroker] Re: AFL programming style questions comments /* */ vs.
//
> Tuzo, Joe,
>
> So if I unde
Tuzo, Joe,
So if I understand this correctly, in my code I use many loops for
complex functions and comment many lines because of the complexity.
If each line I comment takes 100 ns and I am running a 50,000 bar
backtest, I could end up with 800 ms of time wasted in // comments!
Since the
--- In amibroker@yahoogroups.com, "J. Biran" <[EMAIL PROTECTED]> wrote:
>
> It was first mentioned in release notes for AB 4.88. also
> quoting from another message:
> > -Original Message-
> > From: [EMAIL PROTECTED] On Behalf Of Tomasz
> Janeczko
> > Sent: Friday, October 20, 2006 12:32 P
ps.com
[mailto:[EMAIL PROTECTED] On Behalf Of tuzo_wilson
Sent: Tuesday, August 05, 2008 10:44 AM
To: amibroker@yahoogroups.com
Subject: [amibroker] Re: AFL programming style questions
--- In amibroker@yahoogroups.com, "J. Biran" <[EMAIL PROTECTED]>
wrote:
>
> Well, as you can tell, I
I, too, would like to have nested /* */ commenting.
As for //, they are great when commenting out only one or two lines.
However, given a large block of code, or a wordy multi-line comment, /*
*/ is what I want to use.
As for compatibility with other programming languages, none of the
langu
--- In amibroker@yahoogroups.com, "J. Biran" <[EMAIL PROTECTED]> 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
rough
Sent: Monday, August 04, 2008 4:56 PM
To: amibroker@yahoogroups.com
Subject: [amibroker] Re: AFL programming style questions
You cannot use anything in the variable name that is
variable. If you
use interval and change the chart interval you won't be able
to
access that variable in the n
Joe, Barry,
I do something like this in my latest flexible Parameters scheme. For
the static variables I use: ParameterName_SECT_ChartID. I add tags to
the parameter file names: pSECT_ParameterName.pva. I put the
parameter files (1 param per file) in folders named:
SetName_TimeFrameCod
You cannot use anything in the variable name that is variable. If you
use interval and change the chart interval you won't be able to
access that variable in the new chart period. Unless that is what you
want to do. Have fun managing them if you do this.
Barry
--- In amibroker@yahoogroups.com
When you use static variables note that if you use the same name in
multiple indicators they can clash. These are system global variables
I think so be careful how you use them.
To prevent this from happening I use a VarPfx variable to make the
variable mane unique. I use the indicator file nam
Herman, Dennis -
try
{
NotepadPP = CodeFolding and CommentFolding
/*
http://sourceforge.net/projects/notepad-plus/
Set language to C for quick test
*/
}
catch
{
// Free - but doesn't save folding status
}
if ( Like )
{
//Lobby for -
AFL = AFL + CodeFolding
> Thanks for pointing that out. I guess I can scratch converting my
> comments off the list for now. It seems that there are only a
>couple
> of remedies for this:
>
> 1. AFL upgrade to nest /* ... */ comments.
> OR
> 2. AFL upgrade to remove // ... EOL comments in preprocessor
I also re
13 matches
Mail list logo
