i can't remember how often this created difficult locatable bugs. a mistyped variablename. i would much more prefer the compiler was shouting at me for beeing such a schmock to use an undecleared variable than to create a new one by accident.
(Implemented as 'EnableExplicit')
[Implemented] dynamic variable creation toogle
-
Froggerprogger
- Enthusiast
- Posts: 423
- Joined: Fri Apr 25, 2003 5:22 pm
- Contact:
Yes, that would be fine.
But I could think of an alternative to implement it inside the compiler:
A switch inside the editor (jaPBE or the official one), which (de)activates this functionality. Realized e.g. just by displaying undeclared variables in another color, e.g. red
But I could think of an alternative to implement it inside the compiler:
A switch inside the editor (jaPBE or the official one), which (de)activates this functionality. Realized e.g. just by displaying undeclared variables in another color, e.g. red
%1>>1+1*1/1-1!1|1&1<<$1=1
Actually Froggerprogger's suggestion is a good one!
In fact, so good I feel like typing it again:
Very Stern TypeCasting is on by default. (Yes!)
It can be turned off within the code.
And if turned off, un-typecast vars are highlighted in the editor.
Neat. Exit many WTF? errors - unless feeling masochistic and specifically asking for it.
* WTF = Why's This Failing? *
In fact, so good I feel like typing it again:
Very Stern TypeCasting is on by default. (Yes!)
It can be turned off within the code.
And if turned off, un-typecast vars are highlighted in the editor.
Neat. Exit many WTF? errors - unless feeling masochistic and specifically asking for it.
* WTF = Why's This Failing? *
-
Froggerprogger
- Enthusiast
- Posts: 423
- Joined: Fri Apr 25, 2003 5:22 pm
- Contact:
Yes, it could be switched by:
So there would be no conflict.
could & would ...
Code: Select all
;TypeCastOn
.
.
;TypeCastOff
.
.
;TypeCastOncould & would ...
%1>>1+1*1/1-1!1|1&1<<$1=1