OS_GetEnv result

John Tytgat John.Tytgat at aaug.net
Fri Aug 2 15:50:48 PDT 2002

In message <e924a55f4b.peter at moo.chocky.org>
          Peter Naulls <peter at chocky.org> wrote:

> In message <3D4A5A57.7040109 at barco.com> John Tytgat wrote:
> > Peter Naulls wrote:
> > 
> > >In message <3D4A53BC.5080409 at esko-graphics.com>
> > >          John Tytgat <JoTy at esko-graphics.com> wrote:
> > >
> > >>BTW, another problem with argv[0] is when you've configured UnixLib to
> > >>get Unix alike file specs, argv[0] is still a RISC OS file spec.
> > >
> > >This is the related issue of course.  A weak symbol may be in order
> > >here.
> >
> > I'm not sure whether I fully understand the purpose of this weak symbol 
> > here.
> Something like the setting for a program's DA heap.  If the symbol is
> created your the program, then unixlib uses a RO pathname, if not (the
> symbol's address is 0), then we unix behaviour on argv[0].

Don't we already have something for this ? __RISCOSIFY_NO_PROCESS in the
__riscosify_control global var.  When set, I would assume to see a
RISC OS filespec in argv[0].  When not set, I would assume to see an
unixified version of the RISC OS filespec, i.e. a Unix filespec.

John Tytgat, in his comfy chair at home                                 BASS
John.Tytgat at aaug.net                             ARM powered, RISC OS driven

More information about the gcc mailing list