On Tue, 1 Jul 2008, Marco van de Voort wrote:
> > On Tue, 1 Jul 2008, Felipe Monteiro de Carvalho wrote: > > I don't see what is difficult about Florians proposition. > > On the contrary, it is the simplest possible solution, > > and quite elegant in my eyes. > > To be honest, I flabbergasted that the two of you agreed on such a runtime > construct. It goes IMHO against Pascal principles. Why ? In your opinion, we must get rid of Array of Const, Variants as well, as well as RTTI ? They all serve the same purpose. No-one will be forced to use the new type, so... > > For the LCL/fpGUI/MSEGui programmers, nothing changes, > > you can even throw away your own conversion routines. > > You need only a single call just prior to passing a string > > to the OS/GUI system: ForceEncoding(). No ifdefs needed, > > all is transparant. > > That's one of the problems. Having to check and insert code for a Tiburon > solution. (that simply will expect UTF-16). The least it should do is have a > way to flag a routine (e.g. by directive/ Tiburon mode) to only accept UTF16 > and insert that call itself. Let's first wait to see what Codegear comes up with, and then worry about compatibility. In my opinion we'll have to write exactly 0 lines of code for this compatibility, with the solution of Florian. Michael. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
