Martin Schreiber schrieb: > On Tuesday 10 November 2009 12:45:26 Michael Schnell wrote: >> Martin Schreiber wrote: >>> Performance and simplicity. MSEgui does not need the overhead of >>> multi-encoding/multi-charsize. At the moment msestring=UnicodeString for >>> FPC 2.4 which is perfect. I fear FPC will drop this simple solution where >>> it was ahead of Delphi. >> Hmmm. I suppose with Linux (using utf-8 for the GUI interface to the >> user programs), having the user program always use Widestring internally >> and convert any GUI input and output string will feature an enormous >> overhead. >> > Xlib and Xft have an utf-16 interface. Windows has an utf-16 interface. > MSEgui > is faster than Lazarus with Gtk2 and even faster as Lazarus with Gtk1 on > Linux IIRC. > >> I feel that just handling the multi-encoding String-management record >> (with "encoding"6 and "character-size", which, in the case of GUI >> generated and "meant for GUI" Strings, always is equal), would not >> impose much overhead over using using the plain old String management >> with just "reference-counter" and "contents-pointer". >> > Did you look into the code in cpstrnew branch? I did.
And which changes are exactly the reason for your concerns? _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
