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

[sjw <simon.j.wright@mac.com>]

On May 2, 11:01 pm, "Ed Falis" <fa...@verizon.net> wrote:
> On Sat, 02 May 2009 16:39:57 -0400, anon <a...@anon.org> wrote:
> > GNAT.OS_LIB existed in GNAT 3.15p  but since GNAT 2005 it have been
> > moved to System.OS_LIB.  And the GNAT.OS_LIB just renames System.OS_LIB
> > which makes this package a legacy for older projects and can be avoided  
> > for
> > future use. It just causes more work for the compiler which increase the
> > compile time.
>
> You're wrong.  GNAT.OS_Lib is the intended interface for users (normally  
> you will get a warning about using an implementation unit subject to  
> unpredictable change if you use System.OS_Lib).  GNAT.OS_Lib is an  
> implementation-defined unit provided to users.  That it is a renaming of  
> System.OS_Lib is irrelevant (and also does not cause any noticable  
> compilation overhead).

With GCC 4.3.3 on Mac OS X,

$ 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).