In our previous episode, Mattias Gaertner said: > > > > I see this as a theoretic consideration. Please give a real world (!) > > code example when this causes a problem. > > Can you give a real world example where a different RTLString for > each platform solves a problem?
It avoids pingpong repeated conversions between OS encoding and whatever encoding is default. > > If you assign the result of an rtl function to an rtlstring, this > > means you don't care about the type of rtlstring[1] or the knowledge, > > that it's type is rtlchar is enough for you. If you assign it to an > > ansistring/widestring whatever, you know what you get. > > What string type will be TStrings.Items and the many other strings in > the classes.pp? IMHO rtlstring. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
