* Re: including <stdlib.h>
@ 1998-02-11 11:23 Kaveh R. Ghazi
1998-02-11 11:23 ` Robert Lipe
1998-02-11 17:22 ` Ross Smith
0 siblings, 2 replies; 6+ messages in thread
From: Kaveh R. Ghazi @ 1998-02-11 11:23 UTC (permalink / raw)
To: jfc, robertl; +Cc: egcs
> From: John Carr <jfc@mit.edu>
>
> The *config.h files I referred to are the autoconf-generated config.h,
> hconfig.h, tconfig.h, and auto-config.h in the gcc build directory.
>
> For example, in auto-config.h replace
> #define HAVE_STDLIB_H 1
> with
> #include <stdlib.h>
John,
This approach removes some of the control one might want since,
if you include auto-config.h, you are forced to include the header file
rather than being able to check a macro. It also removes the ability of
a config/ directory file from being able to override what autoconf tells
us.
Another approach would be to supply a "system.h" file which
includes various headers (eg stdlib.h), provides possibly missing system
prototypes (eg bcopy) and possibly missing system macros (eg R_OK),
etc., and each gcc source file could then include this file if desired
to get default stuff. (Or the source file could instead enumerate these
things manually if the default system.h is not appropriate.)
I've submitted a draft version of this to Jeff, mostly copied
from the same approach used in the fileutils package.
Hmmm, I just checked the list archive and for some reason the
file I submitted seems to have stripped all the include statements so
they appear without the file its trying to include inside <>. Wierd...
Thanks,
--Kaveh
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu ICon CMT Corp.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: including <stdlib.h>
1998-02-11 11:23 including <stdlib.h> Kaveh R. Ghazi
@ 1998-02-11 11:23 ` Robert Lipe
1998-02-11 17:22 ` Ross Smith
1 sibling, 0 replies; 6+ messages in thread
From: Robert Lipe @ 1998-02-11 11:23 UTC (permalink / raw)
To: Kaveh R. Ghazi, jfc; +Cc: egcs
> Another approach would be to supply a "system.h" file which
> includes various headers (eg stdlib.h), provides possibly missing system
> prototypes (eg bcopy) and possibly missing system macros (eg R_OK),
> etc., and each gcc source file could then include this file if desired
> to get default stuff. (Or the source file could instead enumerate these
> things manually if the default system.h is not appropriate.)
This would ease maintenance costs, but would presumably cost us
something during the compilation phase becuase then everything that
includes systems.h also picks up a presumably non-small amount of header
stuff that it now gets to preprocess. I don't know what that cost
actually is in measureable terms, and we might decide it's worth it.
I just wanted to throw it out for discussion.
Personally, if the cost is anything less than horrible, I'm inclined
to support a migration to it.
> Hmmm, I just checked the list archive and for some reason the
> file I submitted seems to have stripped all the include statements so
> they appear without the file its trying to include inside <>. Wierd...
I've noticed that on the web archives. I assumed it was the
html-ification process not correctly replacing those characters with <
and > so as to escape them from tags.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: including <stdlib.h>
1998-02-11 11:23 including <stdlib.h> Kaveh R. Ghazi
1998-02-11 11:23 ` Robert Lipe
@ 1998-02-11 17:22 ` Ross Smith
1998-02-12 4:26 ` Mark Mitchell
1 sibling, 1 reply; 6+ messages in thread
From: Ross Smith @ 1998-02-11 17:22 UTC (permalink / raw)
To: egcs
Kaveh R. Ghazi wrote:
>
> Hmmm, I just checked the list archive and for some reason the
> file I submitted seems to have stripped all the include statements so
> they appear without the file its trying to include inside [angle > brackets]. Wierd...
The list archive is returning the documents as HTML, but neglecting to
replace less-than and greater-than (and maybe ampersand too, I haven't
checked) with the appropriate entity codes.
--
Ross Smith ............................. < mailto:ross.smith@nz.eds.com >
Internet and New Media, EDS (New Zealand) Ltd., Wellington, New Zealand
"Isn't it interesting that the same people who laugh at science fiction
listen to weather forecasts and economists?" -- Kelvin Throop III
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: including <stdlib.h>
1998-02-11 17:22 ` Ross Smith
@ 1998-02-12 4:26 ` Mark Mitchell
1998-02-12 20:07 ` HTML archives (was: Re: including <stdlib.h>) Ross Smith
0 siblings, 1 reply; 6+ messages in thread
From: Mark Mitchell @ 1998-02-12 4:26 UTC (permalink / raw)
To: Ross Smith; +Cc: egcs
>>>>> "Ross" == Ross Smith <ross.smith@nz.eds.com> writes:
Ross> Kaveh R. Ghazi wrote:
>> Hmmm, I just checked the list archive and for some reason the
>> file I submitted seems to have stripped all the include
>> statements so they appear without the file its trying to
>> include inside [angle > brackets]. Wierd...
Ross> The list archive is returning the documents as HTML, but
Ross> neglecting to replace less-than and greater-than (and maybe
Ross> ampersand too, I haven't checked) with the appropriate
Ross> entity codes.
This is kind-of a feature. I actually suggested doing things this way
early on because it means you can save (as source) a patch and patch
your sources with it. If the '<' became '<' that wouldn't be
possible. Perhaps the CVS server obsoletes this, but perhaps not;
it's sometimes nice to be able to try out someone's patch, or assist
them with it, before it's ready to be checked in. Ideally, of course,
we'd have both...
Ross> -- Ross Smith
Ross> ............................. < mailto:ross.smith@nz.eds.com >
Ross> Internet and New Media, EDS (New Zealand) Ltd., Wellington,
Ross> New Zealand "Isn't it interesting that the same people who
Ross> laugh at science fiction listen to weather forecasts and
Ross> economists?" -- Kelvin Throop III
--
Mark Mitchell mmitchell@usa.net
Stanford University http://www.stanford.edu
^ permalink raw reply [flat|nested] 6+ messages in thread* HTML archives (was: Re: including <stdlib.h>)
1998-02-12 4:26 ` Mark Mitchell
@ 1998-02-12 20:07 ` Ross Smith
1998-02-13 2:04 ` Richard Henderson
0 siblings, 1 reply; 6+ messages in thread
From: Ross Smith @ 1998-02-12 20:07 UTC (permalink / raw)
To: egcs
Mark Mitchell wrote:
>
> >>>>> "Ross" == Ross Smith <ross.smith@nz.eds.com> writes:
>
> Ross> The list archive is returning the documents as HTML, but
> Ross> neglecting to replace less-than and greater-than (and maybe
> Ross> ampersand too, I haven't checked) with the appropriate
> Ross> entity codes.
>
> This is kind-of a feature. I actually suggested doing things this way
> early on because it means you can save (as source) a patch and patch
> your sources with it. If the '<' became '<' that wouldn't be
> possible. Perhaps the CVS server obsoletes this, but perhaps not;
> it's sometimes nice to be able to try out someone's patch, or assist
> them with it, before it's ready to be checked in. Ideally, of course,
> we'd have both...
I don't understand the problem. Netscape, and I assume any web browser,
can save a page as plain text, which converts the HTML entities back
into characters.
(Please don't mail to me as well as the list, it just means I get it
twice.)
--
Ross Smith ............................. < mailto:ross.smith@nz.eds.com >
Internet and New Media, EDS (New Zealand) Ltd., Wellington, New Zealand
"Isn't it interesting that the same people who laugh at science fiction
listen to weather forecasts and economists?" -- Kelvin Throop III
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1998-02-13 2:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-02-11 11:23 including <stdlib.h> Kaveh R. Ghazi
1998-02-11 11:23 ` Robert Lipe
1998-02-11 17:22 ` Ross Smith
1998-02-12 4:26 ` Mark Mitchell
1998-02-12 20:07 ` HTML archives (was: Re: including <stdlib.h>) Ross Smith
1998-02-13 2:04 ` Richard Henderson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).