public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruce Korb <korbb@datadesign.nospam.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: egcs@cygnus.com
Subject: RE: Include Hackery
Date: Tue, 02 Sep 1997 11:26:00 -0000	[thread overview]
Message-ID: <340C5A11.78BE@datadesign.nospam.com> (raw)

Ian Lance Taylor wrote:

> The only problem I saw in a quick glance is that using functions in sh
> scripts is unfortunately nonportable.

I am not a portable shell expert.  In fact, I mostly use ksh.
Anyway, I'll regen it and embed it inside the main loop
for anyone that needs it that way.

> In general, this seems like a very promising approach.  It would be
> nice if people on different systems could compare this to the
> traditional fixincludes script.
> 
> You can run
>     fixincludes foo /usr/include

Thanks.  This is what I was hoping people would do.

> Any differences would presumably require investigation.

I can tell you of two that I know about:
1.  the "#undef NULL" inserted before "#define NULL" is left-justified
2.  The commentary to the right of "#else" and "#endif" used to
    be stripped.  I put it inside "/* */".

-- 
Bruce Korb                      | Data Design Systems, Inc.
Korbb at DataDesign dot com     | 45 Cabot Dr., Suite 110
Voice:  408-260-0280            | Santa Clara,  CA   95051
Fax:    408-260-0281            | USA

             reply	other threads:[~1997-09-02 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-02 11:26 Bruce Korb [this message]
1997-09-02 15:47 ` Jim Wilson
1997-10-06  9:05   ` Include Hackery is dead :-( Bruce Korb
1997-10-07 23:14     ` Jeffrey A Law
     [not found] <340871EF.6B4F@datadesign.nospam.com>
1997-09-02 10:52 ` include hackery Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
1997-08-30 12:00 Incorrect i960 linker config Stephen Williams
1997-08-30 19:18 ` include hackery Bruce Korb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=340C5A11.78BE@datadesign.nospam.com \
    --to=korbb@datadesign.nospam.com \
    --cc=egcs@cygnus.com \
    --cc=ian@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).