From: Thorsten Glaser <tg@66h.42h.de>
To: binutils@sources.redhat.com
Subject: Re: Remove parameter names from libiberty.h
Date: Fri, 15 Apr 2005 07:34:00 -0000 [thread overview]
Message-ID: <Pine.BSO.4.61L.0504150728360.1488@thor.66h.42h.de> (raw)
In-Reply-To: <20050414101938.GA28001@tetto.home>
Marc Espie dixit:
>C is an annoying language without enough namespaces, and where the
>preprocessor can tramp all over the place.
Such as
| Apr 16 OpenBSD/1 is ELF, 2003
in calendar(1), right?
(i386 got predefined by cpp)
//mirabile
next prev parent reply other threads:[~2005-04-15 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 10:20 Marc Espie
2005-04-15 7:34 ` Thorsten Glaser [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 15:21 Paul Schlie
2005-04-14 16:18 ` Andrew Pinski
2005-04-14 17:18 ` H. J. Lu
2005-04-14 17:50 ` Dave Korn
2005-04-14 20:58 ` Ian Lance Taylor
2005-04-12 1:21 libiberty.h Alan Modra
2005-04-13 23:57 ` Remove parameter names from libiberty.h Kaveh R. Ghazi
2005-04-14 1:13 ` Ian Lance Taylor
2005-04-14 7:42 ` Thorsten Glaser
2005-04-14 12:41 ` DJ Delorie
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=Pine.BSO.4.61L.0504150728360.1488@thor.66h.42h.de \
--to=tg@66h.42h.de \
--cc=binutils@sources.redhat.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).