[fpc-devel] Unicode paths

[Sven Barth]

Am 12.04.2016 18:46 schrieb "Marco van de Voort" <marcov at stack.nl>:
>
> In our previous episode, Michael Van Canneyt said:
> > >> If argv/argc is known to be UTF8 encoded, then I see no problem with
> > >> keeping getopts ?
> > >
> > > Getopts is not utf8 but shortstring, so ACS on Windows. Or do you
plan to
> > > redo it using utf8string or unicodestring?
> >
> > I don't necessarily plan to do so, I was proposing it as a way out.
>
> If getopts is not leading, then the needs of the unicode
T(Custom)Application
> classes is probably the best indicator for which way to go.
>
> If they don't need argv and argc, just leave them as they are.
>
> Anyway, I never liked the fact that argv and argc are exported symbols. If
> they weren't public, we could change them at will and/or have differing
> implementations and encodings depending on target.  I would deprecate them
> (being public)

Agreed. They are only exported for ObjPas and that can be solved in the
same way as other symbols uses there are solved.

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20160412/44ad8361/attachment.html>