Re: [fpc-devel] The (near) future of strings

In our previous episode, Sven Barth said: > > source dir is read-only. If you start building sources multiple times in > one > > run, that is a good way. > > > > That's part of the build system. Yes it is, and that is what I meant. ___ fpc-devel

Re: [fpc-devel] The (near) future of strings

Am 07.03.2016 19:16 schrieb "Michael Van Canneyt" : > > > > On Mon, 7 Mar 2016, Marco van de Voort wrote: > >> In our previous episode, Michael Van Canneyt said: However in Michael's scheme with Sysutils using Ansi and System.Sysutils using unicodestring

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Marco van de Voort wrote: In our previous episode, Michael Van Canneyt said: /usr/local/lib/fpc/4.0.0/x86_64-linux/dotted/XYZ But only one is referenced in fpc.cfg : #IFDEF NAMESPACED /usr/local/lib/fpc/4.0.0/x86_64-linux/dotted/XYZ #ELSE

Re: [fpc-devel] The (near) future of strings

In our previous episode, Michael Van Canneyt said: > /usr/local/lib/fpc/4.0.0/x86_64-linux/dotted/XYZ > > But only one is referenced in fpc.cfg : > > #IFDEF NAMESPACED > /usr/local/lib/fpc/4.0.0/x86_64-linux/dotted/XYZ > #ELSE > /usr/local/lib/fpc/4.0.0/x86_64-linux/XYZ > #ENDIF > > where the

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Florian Klämpfl wrote: I hope somebody implements this in fpmake :) My "subarch" directory approach needed by several targets is already on hold for years as I do not owe to touch fpmake regarding this. I don't understand why ? Why would you not touch fpmake for this

Re: [fpc-devel] The (near) future of strings

Am 07.03.2016 um 19:16 schrieb Michael Van Canneyt: > > > On Mon, 7 Mar 2016, Marco van de Voort wrote: > >> In our previous episode, Michael Van Canneyt said: However in Michael's scheme with Sysutils using Ansi and System.Sysutils using unicodestring this will fail. >>> >>> Why

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Marco van de Voort wrote: In our previous episode, Michael Van Canneyt said: However in Michael's scheme with Sysutils using Ansi and System.Sysutils using unicodestring this will fail. Why would this fail ? All we need to do is introduce -NS ? If you have a mix of

Re: [fpc-devel] The (near) future of strings

In our previous episode, Michael Van Canneyt said: > > > > However in Michael's scheme with Sysutils using Ansi and System.Sysutils > > using unicodestring this will fail. > > Why would this fail ? All we need to do is introduce -NS ? If you have a mix of generations (as is currently possible

Re: [fpc-devel] The (near) future of strings

Am 07.03.2016 15:00 schrieb "Marco van de Voort" : > > In our previous episode, Michael Van Canneyt said: > > 2. Provide Delphi-compatible dotted units, with string = widestring. > > > > Basically, the user has then 2 choices: > > 1. is the pre-delphi 2009 option, > > 2. is the

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Marco van de Voort wrote: DXE2+ also allow to introduce the scopeprefix so that you don't need to use dotted units (iow if you uses sysutils, then System.sysutils.dcu is found etc). So I use @dcc32 "-NSSystem;System.Win;WinAPI;Vcl;Vcl.Imaging;Data;VclTee" %1 %2 %3 %4 %5

Re: [fpc-devel] The (near) future of strings

In our previous episode, Mattias Gaertner said: > >[...] > > > Do you mean the dotted unitname will not be needed when the compiler > > > is extended to support namespace prefixes (project and command line > > > switch)? > > > > I assume not since that would be Delphi incompatible. Under delphi

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016 15:23:01 +0100 (CET) mar...@stack.nl (Marco van de Voort) wrote: >[...] > > Do you mean the dotted unitname will not be needed when the compiler > > is extended to support namespace prefixes (project and command line > > switch)? > > I assume not since that would be Delphi

Re: [fpc-devel] The (near) future of strings

In our previous episode, Mattias Gaertner said: > >[...] > > I usually use Delphi XE2+ with namespace prefix, and many with me. IMHO > > requiring to change Delphi sources to dotted units is a nono. > > What do you mean with Delphi sources? The Classes unit or the > user's unit? User code that

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016 15:00:01 +0100 (CET) mar...@stack.nl (Marco van de Voort) wrote: >[...] > I usually use Delphi XE2+ with namespace prefix, and many with me. IMHO > requiring to change Delphi sources to dotted units is a nono. What do you mean with Delphi sources? The Classes unit or the

Re: [fpc-devel] The (near) future of strings

In our previous episode, Michael Van Canneyt said: > 2. Provide Delphi-compatible dotted units, with string = widestring. > > Basically, the user has then 2 choices: > 1. is the pre-delphi 2009 option, > 2. is the Delphi 2009 and higher option > > Both units can be created using a single

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Mattias Gaertner wrote: On Thu, 03 Mar 2016 06:35:35 + Alfred wrote: [...] In the (near) future, I am still a very happy user of FPC. And mORMot. And sometimes some version of Delphi > XE2. Lets say its 2017. And I am using FPC 3.2.0. Or FPC 4.0.

Re: [fpc-devel] The (near) future of strings

On Mon, 7 Mar 2016, Alfred wrote: I was assuming that a goal (first quote: UTF16) would be accompanied by (some sort of) a roadmap. Opinions are divided, hence there is no roadmap. The main point is what to do with backwards compatibility. Most people do not want to give this up. There

[fpc-devel] The (near) future of strings

I was assuming that a goal (first quote: UTF16) would be accompanied by (some sort of) a roadmap. Perhaps I am wrong. But, again, a comment on the remaining quotes would be welcome. And also a comment on the use of {$mode delphiunicode}. ___

[fpc-devel] The (near) future of strings

Mmmm ... not that many answers ... Let me try another question: does the link below correctly state the current use and especially future of FPC / Lazarus ? http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus Especially (quotes): * The goal of FPC project is to create a Delphi