> Danny Braniss wrote:
>
> > now why would FreeBSD supply sources?
> > from /usr/src/lib/libc/stlib/getenv.c:
> > ...
>
> Thanks I have the source but actually checking the call programatically
> should be better since since it does not rely on my interpretation
> of code. It also does not help
Danny Braniss wrote:
now why would FreeBSD supply sources?
from /usr/src/lib/libc/stlib/getenv.c:
...
Thanks I have the source but actually checking the call programatically
should be better since since it does not rely on my interpretation
of code. It also does not help me understand the pro
Thanks for the reference. As I read it FreeBSD is following
standard (no surprise ;-) but it would appear other platforms
may not be. I'll check this out when I get access to a linux
box.
Joseph Koshy wrote:
From "The Open Group Base Specifications Issue 6"
http://www.cnop.net/docs/susv3/fun
> Hello,
>
> I am trying to create a port of some 3rd party software and while
> I can get it to compile ok and (mostly) run there are a few anomalies in
> it detecting environment variables. It appears to run ok on linux (I do
> not have a convenient linux box for testing with). I believe its t
> Is this analysis correct? Can someone point me to the (a?)
> standard that describes this. The FreeBSD behaviour makes
> sense, I am trying to understand what is the expected
> behaviour on other platforms.
>From "The Open Group Base Specifications Issue 6"
http://www.cnop.net/docs/susv3/funct
5 matches
Mail list logo
