Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread D2007 -> D2010
Wed, Sep 2 2009 5:09 AMPermanent Link

Uli Becker
Hi,

I need an advice from the experts using D2009 or D2010.

Since I haven't dealed with unicode now (I write my applications just in
my language): can I use the same code in D2010 like I did in D2007? IOW:
have I to use unicode or is it just optional? And: have I to use the
unicode version of EDB as well?

Thanks in advance...

Uli
Wed, Sep 2 2009 6:11 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Uli


From my reading of newsgroups rather than any active use I don't think your app HAS to be unicode. What you do have to do, however, if you want to stay non-unicode is all references to string, char and pchar will have to be changed to ansistring etc.

If you do that and stay with the non-unicode version of ElevateDB it will be your responsibility to make sure the data that gets sent to ElevateDB is non-unicode.

Oh yes don't forget any other 3rd party stuff you have will need to have been converted for D2009/D2010 operation


Roy Lambert
Wed, Sep 2 2009 6:44 AMPermanent Link

Uli Becker
Roy,

> What you do have to do, however, if you want to stay non-unicode is all
references to string, char and pchar will have to be changed to
ansistring etc.
> If you do that and stay with the non-unicode version of ElevateDB it will be your responsibility to make sure the data that gets sent to ElevateDB is non-unicode.

OK, that doesn't seem to be a big deal.

> Oh yes don't forget any other 3rd party stuff you have will need to have been converted for D2009/D2010 operation

Right - there are some (!) components to be converted.

Thanks Uli
Wed, Sep 2 2009 7:11 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Uli


Report back on how big a deal it is Smiley Also I'd suggest you wait for any other comments about using non-unicode ElevateDB

Roy Lambert
Wed, Sep 2 2009 8:05 AMPermanent Link

Uli Becker
Roy,

> Report back on how big a deal it is Smiley

I will!

> Also I'd suggest you wait for any other comments about using non-unicode ElevateDB

Yes - would be interesting. No problem since I am not in a hurry.

Uli
Wed, Sep 2 2009 12:59 PMPermanent Link

"Malcolm"
Uli Becker wrote:

> Hi,
>
> I need an advice from the experts using D2009 or D2010.
>

Well that rules me out!  Surprised

I am in the middle of converting from D2006 to D2009.

In D2009+, unicode is *hard* to avoid.  If you want to stay ansi,
don't upgrade.

However, if you can fully switch over to unicode you will not have a
lot of trouble - most of your old code will run as before.
If you use Windows API calls you will need to be sure you use the
correct pointer types.
You may get some warnings about string functions that should be
replaced with new versions.

Unfortunately I have to communicate with hardware devices over serial
lines and for that I need to generate or convert from unicode to ansi
or even ascii which is a pain.

In the longer term unicode is the way to go.  Windows is unicode, so
.... <shrug>

Read Marco Cantů's White Paper, Delphi and Unicode (November 2008)
and the 3 papers Nick Hodges wrote and blogged about last year on
this topic.

Malcolm

--
Wed, Sep 2 2009 1:54 PMPermanent Link

Uli Becker
Malcolm,

> I am in the middle of converting from D2006 to D2009.
> In D2009+, unicode is *hard* to avoid.  If you want to stay ansi,
> don't upgrade.

I guessed that.

> Read Marco Cantů's White Paper, Delphi and Unicode (November 2008)
> and the 3 papers Nick Hodges wrote and blogged about last year on
> this topic.

Thanks for this - just downloading it.

Regards Uli
Image