Permission and scope are the same thing. If you can't see it (i.e. out of
scope), you can't use it. If you can see it (i.e. in scope), you can use it.
Otherwise I agree. The existing functionality is very powerful, particularly
when used in combination with dynamic variables.
My comments were s
o write tons of code to do simple thing, use eSignal and JScript.
I would stay with AFL and save my fingers from ache.
Best regards,
Tomasz Janeczko
amibroker.com
- Original Message -
From: "scourt2000"
To:
Sent: Friday, November 06, 2009 10:56 AM
Subject: [amibroker] Re: Biggest sh
"But if I were the developer of AFL, it would really bother me and I would
fix it so that AFL were easier to read and code."
I'm sure if you were the developer, you would quickly change your mind.
The man would have a million conflicting priorities. While this feature you
are discussing I would c
Tomasz,
First off, if we're talking about programming languages in-the-large, I have no
earthly idea why you ever decided that global variables in a script should not
be remembered between runs of that script. It was your decision as a language
designer to diverge from standard implementa
I'd like to address what I see as a flaw in the logic of the original post, as
well as a suggestion to Tomasz's reply.
There are perhaps more Java developers now than C++ developers. For the true
equivalent of StaticVarGet/Set, the Java keyword "public" would work very
nicely (as opposed to "sh
I actually think what you are suggesting - which is essentially typing a few
less characters - has the potential to lead to huge confusion when writing a
lot of code. Also potentially difficult to debug... should you accidentally get
your static & non-static variables mixed up...
At least with
