The idea of private and public seems unnecessary for mIRC scripting. For a language that has always tried to be easy to pick up the use of private/public seems counter-productive. Same too for constants - there'll clearly be no performance benefit to them so there's no need to limit the scripters ability. For both public/private variables and constants If the scripter knows what they're doing then there's no reason not to allow them access to change
any variable, and if they don't know what they're doing they either shouldn't be doing it or should be ready to see things break in the name of learning.
If classes are just going to be static then it seems you might aswell use the existing ability to use periods in aliases and stick to a
class.method naming convention.
Trying to change a constant should be quitely ignored.
If something fails it should raise an error. Trying to sweep errors under the carpet just encourages bugs.
