TD5.1 Unicode paper attached

Discussions specific to Team Developer 5.1.

TD5.1 Unicode paper attached

Postby apaula » Mon Jan 07, 2008 2:36 pm

Hello All,

Please find attached a TD5.1 Unicode paper addressing questions and Unicode-related issues discussed in this forum.

Best Regards,
Ana
--
Unify Technical Support
You do not have the required permissions to view the files attached to this post.
apaula
Site Admin
 
Posts: 1164
Joined: Wed Feb 14, 2007 2:22 pm
Location: UK

Re: TD5.1 Unicode paper attached

Postby mvandine » Wed Jan 09, 2008 2:34 am

Thanks for sharing, Ana!!
Mike Vandine
Gupta Technologies
User avatar
mvandine
 
Posts: 4120
Joined: Wed Feb 14, 2007 4:15 pm
Location: Perth, Western Australia

Re: TD5.1 Unicode paper attached

Postby Stefan Giurgiu » Fri May 09, 2008 3:23 am

In page 5 of this document, it says:
Unicode paper wrote:Team Developer programmers were always responsible for setting the appropriate receive buffer size by calling SalStrSetBufferLength( ) so, migrating such an application to Team Developer 5.1 will require that the programmer re-evaluates the buffer size and adjust it to be at least double its size.

But in here -- http://support.guptatechnologies.com/supportforum/viewtopic.php?f=18&t=1423&p=3830&hilit=salsetbufferlength#p3830 -- we have this huge story we can summarize like:
- SalStrSetBufferLength() actually sets the double sized buffer by itself so programmers don't need to change their code...
- ...but this shouldn't have happened so it was recorded as a bug, TD-4175...
- ...but it was not fixed as claimed, with SP 2...

We would really appreciate an answer regarding this. Should we change our code to double the buffer size, but wait for SP 3 that makes SalStrSetBufferLength() NOT set the double size by itself? Or, the functionality is correct, the help is correct ("If strString is expected to contain a string value rather than binary bytes, be sure to set nlength equal to the expected number of characters [..]") but you confused us with this attached paper that says the opposite :)
CDK Global's little soldier
Stefan Giurgiu
 
Posts: 232
Joined: Wed Oct 31, 2007 7:16 am
Location: Finland, Oulu

Re: TD5.1 Unicode paper attached

Postby apaula » Tue May 13, 2008 3:48 pm

Hello,

Sorry about the confusion. The bug was found after the white paper was written. I'll make sure that it gets updated.

To clarify: SalStrSetBufferLength() indeed doubles the buffer length passed as parameter. This ended up not being the best approach in many situations so in TD5.1 SP2 we've introduced two new functions:

SalSetBufferLength()
SalGetBufferLength()

The new function SalSetBufferLength() DOES NOT double the length passed as parameter. So it's up to the developers to take care of handling the buffer size when dealing with Unicode data.

We recommend that developers use these two new functions from SP2 and on. The old SalStrSet/GetBufferLength equivalents will be deprecated in the near future.

Hope this clarifies a bit.
Ana
apaula
Site Admin
 
Posts: 1164
Joined: Wed Feb 14, 2007 2:22 pm
Location: UK

Re: TD5.1 Unicode paper attached

Postby apaula » Tue May 13, 2008 3:51 pm

I've removed the attached doc and will re-load it as soon as it's updated.

Thanks for your comprehension,
Ana
--
Unify Technical Support
apaula
Site Admin
 
Posts: 1164
Joined: Wed Feb 14, 2007 2:22 pm
Location: UK

Re: TD5.1 Unicode paper attached

Postby Stefan Giurgiu » Tue May 13, 2008 9:19 pm

OK things look much more clear now.
CDK Global's little soldier
Stefan Giurgiu
 
Posts: 232
Joined: Wed Oct 31, 2007 7:16 am
Location: Finland, Oulu


Return to Team Developer 5.1

Who is online

Users browsing this forum: No registered users and 1 guest

cron