Ian Bicking wrote:
> One alternative would be to make TS more future-compatible, but
> versioning the input. I remember browsing some discussion on the
> Python lists. One person noted a system that had a version at the top
> the file, and would sometimes edit the code in-place or put in
> backward compatible features. This way the new syntax could delete
> things, while the old syntax could still work.
Another way to handle this would be to create an upgrade script whenever
the syntax/interface changes significantly. The script would translate
the old syntax to the new, and you could go on your merry way with the new
features.
> Anyway, I think you shouldn't even *talk* about a freeze date until
> you really know what you are working towards. I think that's still up
> in the air for both of the important parts of Cheetah -- the syntax,
> and the interface. 1.0 means these shouldn't change for a while.
well said
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
