Team Developer 5.1 Highlights

forum.marketing.feedback (2000-2005) & forum.gupta.marketing (2005-2010)
Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 12 Apr 2007, 16:20

 Posted by:  Martin Teetz 


As far as I know it will look like the TD 4.2 Table Window.

Martin

Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 12 Apr 2007, 16:23

 Posted by:  Martin Teetz 


Hi Michael,

Unicode will be a integral part of TD 5.1, not a choice to use.
The code base of TD 5.1 is TD 4.2.

Martin

Scott
Australia
Posts: 375
Joined: 13 Mar 2017, 23:31
Location: Sydney, Australia

Team Developer 5.1 Highlights

Post by Scott » 13 Apr 2007, 01:46

 Posted by:  Scott Booth 

Will that have an impact on existing CStruct, Windows & 3rd party DLLs and
will it be a requirement to use the international version of SQLBase?

micsto
Germany
Posts: 738
Joined: 07 Mar 2017, 16:07
Location: Germany

Team Developer 5.1 Highlights

Post by micsto » 13 Apr 2007, 08:36

 Posted by:  Michael Stoll \(MICSTO\) 

Hi Martin,

does it mean that every HSTRING in 5.1 will be a UNICODE string, or will
there be a dedicated datatype for UNICODE strings, e.g. UHSTRING, and the
"old" HSTRING remains unchanged?

Michael

Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 13 Apr 2007, 15:51

 Posted by:  Martin Teetz 


You do not need SQLBase International for TD 5.1. TD 5.1 will come with
a SQLBase 9.x database bundled.
For the other things I need to ask Engineering. I'll come back with an
answer for you.

Martin

Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 13 Apr 2007, 15:52

 Posted by:  Martin Teetz 

Hi Michael,

I need to find out. You will get an answer soon.

Martin

Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 17 Apr 2007, 09:25

 Posted by:  Martin Teetz 


Michael and All,

Here is a first summary of how interfacing with TD 5.1 will work. We
will be creating a Guide for third party tool providers that explains
what needs to be done. From what I can figure out, the effort should be
pretty small for third party tool providers. Also all Third Party
providers are invited to an early beta program of TD 5.1 when the
Unicode work is done. We want to make sure you can provide your tools
ready for TD 5.1 when we release the product.

Internally all text will be kept as Unicode (wchar_t), this includes
HSTRING’s. New SWin HString functions will be supplied that are
specifically for Unicode. When getting and writing to a HSTRING buffer a
lock or allocate function is called, we will need to reintroduce a
unlock function that we will know when the buffer is finished being
manipulated and (possibly) translated to Unicode.

We will supply ASCII versions of most string functions in our API that
will essentially convert to Unicode and call the Unicode versions. The
list of our API calls has not been finalized but includes about 200
functions. When including our headers if Unicode is defined then our Sal
calls will be mapped via macros to the Unicode versions, if Unicode is
not defined they will be mapped to the local code page versions.

Third party products that use OS calls will to do string operations on
our windows can also rely on this same defines. i.e. If Unicode is
defined then GetWindowText( ) will get Unicode if Unicode is not defined
it is local code page.

We will be introducing a new datatype(s) for third party dll’s that will
accommodate wchar_t and wchar_t*. The interpreter will be smart enough
to distinguish as long as the correct datatype is used in the external
declaration section.

Let me know if you have any questions.
Best regards,
Martin

micsto
Germany
Posts: 738
Joined: 07 Mar 2017, 16:07
Location: Germany

Team Developer 5.1 Highlights

Post by micsto » 17 Apr 2007, 14:05

 Posted by:  Michael Stoll \(MICSTO\) 

Hi Martin,

first of all many thanks for your detailed answer.
Altogether it sounds really good, though the need to unlock HSTRING's in 5.1
is a little bit "unlovely".

Nevertheless, I have some questions:

1. What about the external function parameter of type LPSTR? Will this be
available in 5.1 to pass ASCII strings?
2. Today there are many Sal functions which have a parameter of type LPSTR,
e.g. SalStrIsValidNumber.
Will the type remain LPSTR in the ASCII version of those functions, or will
it be changed to HSTRING?

Michael

Martin Teetz

Team Developer 5.1 Highlights

Post by Martin Teetz » 18 Apr 2007, 09:09

 Posted by:  Martin Teetz 

Hi Michael,

Engineerings answer to your questions:

>>1. What about the external function parameter of type LPSTR? Will
this be available in 5.1 to pass ASCII strings?

Yes. LPSTR will be available in external parameter type.
You can pass ASCII string to external function. There will be conversion
from wide char to ascii.
Since TD runtime in 5.1 handles string as wide character, runtime will
convert wide char to ASCII string and pass it to the external function.

>>2. Today there are many Sal functions which have a parameter of type
LPSTR, e.g. SalStrIsValidNumber.
>>Will the type remain LPSTR in the ASCII version of those functions,
or will it be changed to HSTRING?

TD 5.1 will provide two version of functions for all functions which has
string parameters. One with ascii string(LPSTR) and another with wide
character string. Header file Sal.h will choose the appropriate version
depending on the configuration.

In ASCII build SalStrIsValidNumber become SalStrIsValidNumberA
In UNICODE build SalStrIsValidNumber become SalStrIsValidNumberW

End user need not to bother to choose the different version. Your old
application will work as it is.

Best regards,
Martin

Return to “gupta.marketing”

Who is online

Users browsing this forum: [Ccbot] and 0 guests