Well, it's definitely on it's way now with SA codes being sent out.
Unfortunately I wont be able to use it in anger for a little while until we complete some current project work.
I must admit to some trepidation in moving to Delphi 2009 from Delphi 2007 due the Unicode changes. We have a large source tree approaching two million lines of code, large pieces of which deal with file format conversion which would be sensitive to ANSI vs Unicode issues...
2 comments:
FWIW, we had a tree of over 5 million lines of Delphi code to convert, both the IDE itself and all the libraries, and it went reasonably well.
Once you get used to the general patterns and idioms of conversion, it goes fairly smoothly - presuming that you don't have deep dependencies on "AnsiString as a managed array of bytes"; but even in those cases, you can get by, by replacing string -> AnsiString.
Hi Barry,
Yes, I think you're right. It still feels a little daunting from the bottom of the hill though ;-)
I guess my main concern regards our many file format conversions is the various subtle interplays of reading data from both binary and text files sensibly depending on the source ANSI/UniCode context.
As you suggest, you can tie a lot of this down with appropriate use of ANSIString/UnicodeString is needed. However, I'm expecting a few 'hilarious' issues to deal with!
5 millions LOC huh? That's a decent sized source tree! I'm glad to hear the conversion went well for you.
Post a Comment