[fpc-devel] String and UnicodeString and UTF8Stringt

Jonas Maebe jonas.maebe at elis.ugent.be
Tue Jan 11 11:11:46 CET 2011

On 11 Jan 2011, at 10:47, Marco van de Voort wrote:

> I still have to study Jonas last message. It seems to indicate that I
> misunderstood what rawbytestring.  If that is true, Jonas is right,
> separating the targets will result in two targets (rawbytestring and
> unicodestring)

Here's some nice explanation about how rawbytestring behaves in  
practice: http://www.micro-isv.asia/2008/08/using-rawbytestring-effectively/

And here's an answer by Barry Kelly to a post about rawbytestring  
explaining what the purpose of the type is (similar to what I said): http://www.codegod.de/WebAppCodeGod/Delphi-2009-RawByteString-vagaries-QID85470.aspx

He mentions using them as parameter types to reduce the number of  
overloads, but I'm still wondering about var-parameters in particular.  
I would guess that it may very well be forbidden to pass an  
ansistring(0) to a rawbytestring var-parameter, so it would still not  
solve everything in that case (and if it's not forbidden, I'm curious  
how you can obtain the statically defined codepage of the  
ansistring(0) at the callee side in case the input string was empty).


More information about the fpc-devel mailing list