Re: GNAT on WinXP: System.OS_Lib.Spawn raises Program_Error

[Robert A Duff <bobduff@shell01.TheWorld.com>]

sjw <simon.j.wright@mac.com> writes:

> $ gnatmake -f -gnatwaL test
> gcc -c -gnatwaL test.adb
> test.adb:7:03: warning: "Program_Name" is not modified, could be
> declared constant
> gnatbind -x test.ali
> gnatlink test.ali
> gnatlink: warning: executable name "test" may conflict with shell
> command
>
> So no warning about implementation-defined units there (I have seen
> them, though).

That's a bug.  GNAT should warn on "with System.OS_Lib;",
but not warn on "with GNAT.OS_Lib;".  The idea is that
if you mention GNAT.<something>, you _know_ you are using
a GNAT-specific package.

The purpose of these renamings is to avoid namespace pollution.
You could have your own user-defined package called GNAT -- perhaps
it was written in Ada 83 days, before GNAT even existed.  Not likely,
but GNAT is a perfectly legal name for a user-defined package.
So we don't want the Ada runtimes to "with GNAT.OS_Lib;" -- instead,
they "with System.OS_Lib;".

- Bob