[fpc-devel] The (near) future of strings
Michael Van Canneyt
michael at freepascal.org
Mon Mar 7 16:00:34 CET 2016
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 %6
>
> in a batchfile and I can use all unit names without scopenames.
>
>
> 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 ?
And obviously the 2 RTLs cannot be mixed.
>
> Worse, one mistake in your sources (e.g. a non qualified forms) and you get
> bunches of "Incompatible Type Forms.TForm, expected VCL.Forms.TForm" style errors.
>
> I think some solution with alternative -Fu settings is to be prefered and
> not abuse an unrelated feature (dotted unitnames) to have both ansi an
> unicodestrings in one install.
The alternative is 4 rtls.
Dotted, ansi
not dotted, ansi
Dotted, unicode
not dotted, unicode.
which is clear nonsense.
Michael.
More information about the fpc-devel
mailing list