Mail Archives: djgpp-workers/2004/08/13/01:14:43
Charles Sandmann wrote:
>
>>> Instead of putting environ in djgpp.djl, could we use a define
>>> statement in a header outside the ansi and posix definitions?
>>
>> I think we cannot do this because Posix explicitly says that
>> environ is not declared in any header.
>>
>> In other words, a Posix program that uses environ is not
>> required to include any system header, and it still can expect
>> environ to be available.
>
> OK, so Posix insists it be there without declaration, but ansi
> says it shouldn't be there ... It seems PROVIDE is the only fix.
But without -ansi (or -std=C99) it is perfectly allowable. It
doesn't need to show up as a global, but only as a third parameter
to main, i.e. as local to main. I still claim the library proper
is inconsequential. It just shouldn't pollute. So the name
change to _environ will do that, and environ never need be defined
in the library modules.
The run time doesn't know, or need to know, how many parameters
main was declared with. It just places one integer and two
pointers on the stack before calling main. Their names are
whatever the program writer placed in the line "int main(....){"
The point is that 'environ' is not in static storage, it is only
in the parameter list of main, under any name you like. Or not.
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
- Raw text -