From: scott@hakuin.boeing.com (Scott Moody)
Subject: Re: ENVIRONMENT VARIABLES, Forest, POSIX
Date: 1996/03/15
Date: 1996-03-15T00:00:00+00:00 [thread overview]
Message-ID: <DoBn2H.Ft1@plato.ds.boeing.com> (raw)
In-Reply-To: dsmith-1403961235300001@dsmith-ppp.clark.net
The question of 'getenv' is obviously easy to solve
by making the direct call to the unix you happen to be compiling
on TODAY. What about those other non-standard unix calls
like 'getwd' -- all those that whenever I try to compile C code
from SunOS to SOlaris I hit.
That was why the POSIX interface seems to be the correct abstraction.
I am somewhat worried also about the Forest copywrite restrictions..
. but am more worried about the 'thick' binding that Forest provides.
I can't look at the POSIX manual, and write Ada code. I have to look at
say Forest, and see how (syntax) they let me access that code.
One answer would be to get Ada.POSIX to do it .. then place it into
the language standard, and push the burdon onto ada compilers to
provide portability..
The ada.command_line is a start at this..
-scott
next parent reply other threads:[~1996-03-15 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dsmith-1403961235300001@dsmith-ppp.clark.net>
1996-03-15 0:00 ` Scott Moody [this message]
1996-03-16 0:00 ` ENVIRONMENT VARIABLES, Forest, POSIX David Emery
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox