Re: Tiburón and FastCode
- From: "Xu, Qian" <"quian[dot]xu"@stud.tu-ilmenau.de>
- Date: Sat, 05 Apr 2008 23:28:50 +0200
Dennis wrote:
Hi>
Hello FastCoders, just a curiosity question, but what kind of concerns
do you have about FastCode routines working with the new VCL coming in
the next release of Delphi?
Nothing yet, but let us discuss what we have to do. Please correct me if I
am wrong.
Functions defined with AnsiString as string type will have no problems
TCharPosFunction = function(Chr : Char; const Str : AnsiString) : Integer;
but functions defined to take or return the type "string" will fail if they
do not support WideString.
TTrimFunction = function (const S: string) : string;
One solution is to test that string=AnsiString prior to calling the
function. Another is to redefine the function prototypes.
TTrimFunction = function (const S: AnsiString) : AnsiString;
IMHO This solution is the correct one.
Why was functions like Trim defined to take and return "string" in the first
place?
Best regards
Dennis Kjaer Christensen
As CodeGear's engineers said "Except user explicit use AnsiString/AnsiChar, string/Char will be mapped to UnicodeString/WideChar automatically."
If FastCode is only designed for ANSI world. It would be useless for Tiburon.
--
Best regards
Xu, Qian (stanleyxu)
http://stanleyxu2005.blogspot.com/
.
- References:
- Tiburón and FastCode
- From: Lee Grissom
- Re: Tiburón and FastCode
- From: Dennis
- Tiburón and FastCode
- Prev by Date: Re: Tiburón and FastCode
- Next by Date: Re: Tiburón and FastCode
- Previous by thread: Re: Tiburón and FastCode
- Next by thread: Re: FastCode Trim B&V 1.0.1
- Index(es):
Relevant Pages
|