When compiling this program http://www.conoce3000.com/Test.pp in Windows receive the following error:

  Test.pp(4,11) Error: Can't determine which overloaded function to call

The problem only happens when I use a utf8 character. What am I doing wrong?
In Linux, the program compile OK.

If you compile with -vh, then the compiler will tell you which function definitions it found:

tt.pp(4,11) Error: Can't determine which overloaded function to call
wstrings.inc(1623,10) Hint: Found declaration: UTF8Encode(const WideString):AnsiString;
ustrings.inc(2281,10) Hint: Found declaration: UTF8Encode(const UnicodeString):AnsiString;

The reason it works on Unix platforms, is that widestring=unicodestring there (so there is nothing to choose between if you pass a wide/unicodechar). You can solve it by typecasting the character explicitly to either widestring or unicodestring.

Jonas

Ok, thanks.
But I'm writing a book about FreePascal in Spanish (http://www.conoce3000.com/html/espaniol/Libros/PascalConFreePascal/Indice.html). And I do not want to write something to discourage the use of the compiler. I apologize if my questions are a bit uncomfortable.

Why WideString is not equal to Unicodestring in Windows?

Luis Fernando Del Aguila Mejía het geskryf:

Why WideString is not equal to Unicodestring in Windows?

WideString is reference counted (for Windows COM reasons). UnicodeString is pretty much the same as WideString, but not reference counted.

Regards,
- Graeme -

I am pretty sure it is the other way around, UnicodeString is the unicode version of AnsiString and is thus reference counted. WideString is the OLEstring compatible string, and is not reference counted.

Vincent

Correct.

Michael.

Vincent Snijders het geskryf:

I am pretty sure it is the other way around, UnicodeString is the unicode version of AnsiString and is thus reference counted. WideString is the OLEstring compatible string, and is not reference counted.

My mistake... only made my first cup of coffee now. :-)

Regards,
- Graeme -

Michael Van Canneyt het geskryf:

In that case the FPC documentation is wrong. Then could you correct the ref documentation please - Section 3.2.5. As quoted below, the docs say WideString is reference counted.

----------[ FPC 2.4 language reference doc ]----------------- 3.2.5 WideStrings
Widestrings (used to represent unicode character strings) are implemented in much the same way as ansistrings: reference counted, null-terminated arrays, only they are implemented as arrays of WideChars instead of regular Chars.
--------------------------------------------------------------

Regards,
- Graeme -

Aloha.... My mistake. Will correct ASAP !!

Michael.

Sorry for highjacking the thread: I take the opportunity to ask about string size. Is it maintained in the data structure, or computed when required? (I mean: is there a notable cost for length()?)

Denis
________________________________

vit esse estrany ☣

spir.wikidot.com