Lite Applications forum

Hi Alvaro and all what you think about having that to all revise the code of a software because of the Unicode of Delphi 2009.

i try to compile one project and receive a million's of warns and erros..

unicode

I think that it was a poor decision. Unicode should be optional. Nobody in the US or in half Europe needs it. By making it mandatory they are giving their customers one more reason not to upgrade.

If they made Delphi a multi-language native platform (Delphi,Java,C#,etc. all native), now that would have some appealing. Imagine something like .NET without the managed/VM crap.

The ONLY improvement related to Delphi 2009 is the PNG native support, but only for TImages and TImageLists (not TBitBtns). To support PNG in TBitBtns you should install PNGComponents and guess what: Delphi 2009 doesn't support it.

UniCode is great for me (I am from non-english country) but I can't accept this delphi version, even if I need UniCode !

Another big problem is that the indy components that comes with Delphi 2009 doesnt fully supports the Unicode, so If you send the emails with some chars used here in brasil for example, all the message comes with a lote of unreadeble chars ... what a mess !

Shame on CG to allow that happen !

fzerorubigd, I really understand your complain. I'm brazilian and a unicode support would also be nice to me. But WHY, my god, WHY can't we see the golden "Delphi 7" times back? I'm with Delphi 7 here and think it will be forever by the way CodeGear treats RAD Studio.

eduardo.sic wrote:Hi Alvaro and all what you think about having that to all revise the code of a software because of the Unicode of Delphi 2009.
i try to compile one project and receive a million's of warns and erros..
unicode

We switched from D7 to D2007 because of memory manager (we could substitute the one in D7), some old odd errors and a new feature "Ribbon Control" (it was a bad idea: it appeared to have incredible number of errors). It was easy: bad IDE, but some programs compiled better without tweaks.

We used TntUnicode, so switching to D2009 seemed to be natural. Some programs failed without warnings, and all the packages had to be adapted to D2009. It seems, that RxLib still isn't updated (however, one should be able to convert to JEDI; I don't know: those programs are not yet being converted to D2009).

API calls (...A-...W functions versions) and Move()-s and Blockread()-s are examples of things that had to be found without warnings, if I remember correctly.