And I highly disagree on the 1.26 mode switches...(till the rest of that post ;-)
I actually didn't suggested that everything without this declaration at the top of the file should be compiled exactly like it did with version 1.24; what the compile would do if it found a "Strict/SuperStirct 1.26" line at the top of the file, is just *hiding* the new keywords. This means the new features still exist and are present, there's just no way to access them, like an operator without a name or symbol associate with it. If you write 'Collection' in your code the compiler refers to it like it was a function/variable... name.But this isn't the thing that caused me to start this thread, it doesn't have to do that much with the subclassing system I suggested. The only reason why I posted it at all was that I tried to avoid posts like "I've written so much code using 'Array' and 'Collection' as variable name, this won't work anymore with this change!"
I wouldn't mind if a plain 'Strict' or 'SuperStrict' statement also activates this changes.