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

[anon@anon.org (anon)]

Ed.

If that was correct, then using "System.OS_LIB" would generated a 
compiler WARNING, but no error or warning is given. So, that package 
is usable as is.

Compiling overhead depends upon how many places packages are used.  
And some people count every cpu cycle. One wasted cycle may be too 
much, and it could cost someone life. I am talking about medical 
operations, such as pin-point radation treatements.



In <op.utbos0e85afhvo@naropa>, "Ed Falis" <falis@verizon.net> writes:
>On Sat, 02 May 2009 16:39:57 -0400, anon <anon@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).
>
>- Ed