Well, as well as all the other useful things that everybody is proposing
how about a sort of Top of the Pops of errors?
My personal favourite crops up all the time:
flase, fales, flsae . . . but, very rarely 'false'
Now . . . variables . . .
Just found 'strict compilation' in my trial of RR 3.5; but couldn't
find anything about what it actually is (which makes Stephen Cox,
who is passing himself off as a Newbie, look much longer in the
tooth than I am).
So; what is 'strict compilation', and why should we be
interested?
Richmond-
Saturday, May 9, 2009, 1:14:47 PM, you wrote:
So; what is 'strict compilation', and why should we be
interested?
Strict compilation was formerly referred to as explictVars.
Setting the checkbox *forces* you to declare all your variables or be
faced with compile errors. The advantage
Writing as someone who, generally, learns from his errors, and
trying to work out why they are error, this sounds as if it would
not be a great advantage to me.
Probably much more useful for somebody trying to belt out
something with a very quick SDLC or turn-around.
Mark Wieder wrote:
Actually I'm not so sure it even matters, considering this isn't a typed
language.
I was just surprised when I ran my first try at code and had errors at
runtime. Almost every compiler I've used checked variables. Why I asked in
the first place.
On 5/9/09 5:24 PM, Richmond Mathewson
Richmond-
Saturday, May 9, 2009, 2:24:47 PM, you wrote:
Writing as someone who, generally, learns from his errors, and
trying to work out why they are error, this sounds as if it would
not be a great advantage to me.
Not to worry - there's plenty of errors to go around...
...I'd be happy to
