public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@cygnus.com>
To: binutils@sourceware.cygnus.com
Subject: Re: A comment-finding hack for hppa I found useful
Date: Tue, 11 Jul 2000 12:10:00 -0000	[thread overview]
Message-ID: <200007111910.MAA17553@elmo.cygnus.com> (raw)

Hi Alan,

:    I found the following hack useful when debugging glibc sources
: for hppa.  The comment in the first hunk below indicates why it's
: useful, but I'm ambivalent as to whether this belongs in the
: official sources.

So basically the problem is that (for the hppa) the comment chracater,
(';') is the same as the line seperator character for lots of other
assemblers, and that tihs leads to confusion, especially when writing
C asm statements ?

I guess I have no objections to adding the feature, although I think
that it will only very occaisionally be useful.  perhaps it could be
part of the output with the -D switch ?

: PS. Question for the language experts.  "#if MACRO" or "#ifdef MACRO",
: which is preferred?  Given MACRO is either undefined or evaluates to 1,
: there is no difference really (except I believe some really old compilers
: don't even supprt #ifdef)

I had not heard about old compilers not supporting #ifdef, but I think
from a very strict point of view, I would prefer '#ifdef MACRO" over
"#if MACRO" since this makes clear that all that is being tested is
the fact that MACRO is defined, not what value it might happen to
have.

Cheers
	Nick

             reply	other threads:[~2000-07-11 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-11 12:10 Nick Clifton [this message]
2000-07-11 13:24 ` Jeffrey A Law
2000-07-11 19:51 ` Alan Modra
2000-07-12 15:37 ` Michael Meissner
2000-07-12 15:48   ` Ulrich Drepper
2000-07-12 18:11   ` Alan Modra
2000-07-27 22:03 ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2000-07-11  1:03 Alan Modra

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=200007111910.MAA17553@elmo.cygnus.com \
    --to=nickc@cygnus.com \
    --cc=binutils@sourceware.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).