Re: ver4 keyword Conflict
- Posted by jimcbrown (admin) Oct 03, 2011
- 1599 views
Jim:
Most code written for 3.11 or earlier is not compatible with ver 4
4.0 was going to break code from earlier versions because of the scope of the changes. Agreement was reached that this would be the very last time that breaking changes should be required though. (At issue was the way namespaces were done.)
(A caveat - some changes planned for 5.0, like object oriented support, might eventually require breaking changes as well. Still, lets hope that lessons learned in the move from 3.11 to 4.0 will be remembered and applied when the time comes.)
Well, I don't think it was quite as absolute as you seem to imply here. I mean, this would preclude just about anything ever being added or changed, language-wise. We do want to minimize breaking changes in minor releases. There will be some new keywords and built-ins, though probably less than what we got with 4.0.
Matt
Well, breaking changes caused by new keywords and such exempted. Those are trivial and can be dealt with in an automated fashion, so having those in minor releases is not a big deal.
