Mark Womack wrote:
Personally, I think that if the new version cannot be binary backwards compatible, it should be a new and separate class and old one should be deprecated. It would be a nasty surprise for people to get a link error at runtime when they upgrade. It's the kind of thing that makes me take developer's names in vain :)Mike,I second Ceki on this. It is still in 1.2.8, and it looks like it is going to get some major attention in v1.3. So, I wouldn't worry too much. But it does sound like it's features/method signature will be changing in v1.3 (depending on the extent of the re-write), but you will get plenty of notice to adjust. Ceki, what about doing the rewrite in the sandbox? -Mark
Ray
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
