From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeffrey A Law <law@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: A comment-finding hack for hppa I found useful 
Date: Tue, 11 Jul 2000 13:24:00 -0000
Message-id: <6126.963347111@upchuck>
References: <200007111910.MAA17553@elmo.cygnus.com>
X-SW-Source: 2000-07/msg00164.html

  In message < 200007111910.MAA17553@elmo.cygnus.com >you write:
  > 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 ?
Yup.  What's just as fun is the line separator is a comment in some
other assemblers, a binary operation, and a completer for certain
instructions :-)

Let's just say PA assembly isn't fun.


  > 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 ?
Possibly.


  > : 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.
Agreed.
jeff