public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: obrien@NUXI.com, aldyh@redhat.com, gcc@gcc.gnu.org,
	jsm28@cam.ac.uk, shebs@apple.com, Richard.Earnshaw@arm.com
Subject: Re: GCC Steering Committee decision on ISO C conversion
Date: Fri, 28 Jun 2002 10:16:00 -0000	[thread overview]
Message-ID: <200206281635.RAA18883@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 28 Jun 2002 10:23:49 EDT." <200206281423.KAA09011@caip.rutgers.edu>


ghazi@caip.rutgers.edu said:
> And I'll let you in on a little secret.  I believe the HP's
> traditional compiler *understands* string concatenation!

> Why do I say this?  Because libiberty/regex.c uses it an no one has
> complained.  Maybe someone can confirm this... 

Actually, regex.c has:

#  if defined (__STDC__) || defined (ALMOST_STDC) || defined 
(HAVE_STRINGIZE)
#   define PREFIX(name) wcs_##name
#   define ARG_PREFIX(name) c##name
#  else
#   define PREFIX(name) wcs_/**/name
#   define ARG_PREFIX(name) c/**/name
#  endif

So traditional compilers can use the traditional pasting method.

That doesn't necessarily mean that the old HPUX C compiler doesn't support 
string pasting, just that you can't use this code as an assertion that it 
does.

R.

  reply	other threads:[~2002-06-28 16:37 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  8:31 Kaveh R. Ghazi
2002-06-13 12:55 ` Neil Booth
2002-06-14  7:02   ` Kaveh R. Ghazi
2002-06-13 14:54 ` Hans-Peter Nilsson
2002-06-13 15:02   ` Gabriel Dos Reis
2002-06-13 18:02     ` Joseph S. Myers
2002-06-14  0:16       ` Gabriel Dos Reis
2002-06-14  7:10   ` Kaveh R. Ghazi
2002-06-13 18:00 ` Phil Edwards
2002-06-14  0:35   ` Florian Weimer
2002-06-14  7:14   ` Kaveh R. Ghazi
2002-06-14  7:28     ` Daniel Berlin
2002-06-13 18:18 ` Joseph S. Myers
2002-06-13 22:29   ` Aldy Hernandez
2002-06-14  7:21     ` Kaveh R. Ghazi
2002-06-14 15:00       ` Eric Christopher
2002-06-27 22:56       ` David O'Brien
2002-06-27 23:43         ` Stan Shebs
2002-06-28  0:34           ` David O'Brien
2002-06-28  9:32         ` Kaveh R. Ghazi
2002-06-28 10:16           ` Richard Earnshaw [this message]
2002-06-28 11:31             ` Andreas Schwab
2002-06-28 11:27               ` Richard Earnshaw
2002-06-14  3:26 ` Richard Sandiford
2002-06-14  7:41 ` Kaveh R. Ghazi
2002-06-14  7:58   ` Dave Hudson
2002-06-14  8:01     ` Alan Lehotsky
2002-06-14  8:22     ` Robert Lipe
2002-06-14  8:12   ` Richard Earnshaw
2002-06-14  8:15     ` Jakub Jelinek
2002-06-14  8:56   ` Richard Sandiford
2002-06-14 14:07     ` Kaveh R. Ghazi
2002-06-27 21:36 ` David O'Brien
2002-06-14  8:46 'David Scott Urban
2002-06-14 10:29 Bonzini
2002-06-22  6:24 Robert Dewar
2002-06-30  4:13 John David Anglin
2002-06-30  5:33 ` Tom Tromey
2002-06-30 12:03 ` Kaveh R. Ghazi
2002-06-30 13:18   ` John David Anglin
2002-06-30 14:55     ` Kaveh R. Ghazi
2002-06-30 18:00       ` John David Anglin

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=200206281635.RAA18883@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=aldyh@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=jsm28@cam.ac.uk \
    --cc=obrien@NUXI.com \
    --cc=shebs@apple.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).