Perhaps, but there's also a lot of other things that COULD be fixed, if it was noted that it might not be entirely backwards compatible.
Actually, this is exactly what RXML in Roxen 2.0 did to RXML. Granted, I didn't like the lack of backwards compatibility but the one major difference is that it's a lot harder to fix broken RXML than it is to fix broken code (which breaks in obvious ways when compiling).
That said, a #version pragma could possibly maintain compatibility too. In either case I think it would more of an efford to update modules to cmods if applicable or at least to use new API's where they don't (and at the same time writing docs for these perhaps :-).
/ David Hedbor
Previous text:
2003-01-06 23:30: Subject: Inconsistency.
/.../ (note, this isn't so different from the stronger type checking and disallowing of equally named local variables - that change broke A LOT of code /.../
On the contrary, they are very different. The difference lies in the benefits and not in the effort to keep old code working. I think the improved error checking is vastly more useful than the avoided dismay over the inconsistency between "is_dir" and "isdir" (or similar naming issues).
/ Martin Stjernholm, Roxen IS