All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] crti.S Nested procedures error
Date: Wed, 03 May 2000 22:45:26 -0600	[thread overview]
Message-ID: <27524.957415526@upchuck> (raw)
In-Reply-To: Your message of Thu, 04 May 2000 11:27:37 +1000. <Pine.LNX.4.21.0005041123510.8334-100000@front.linuxcare.com.au>


  In message <Pine.LNX.4.21.0005041123510.8334-100000@front.linuxcare.com.au>yo
u write:
  > On Wed, 3 May 2000, Jeffrey A Law wrote:
  > 
  > > '!' is the standard comment character for the PA assembly syntax.
  > 
  > sourceware.cygnus.com CVS gas/config/tc-hppa.c has
  > 
  > const char comment_chars[] = ";";
  > const char line_separator_chars[] = "!";
  > 
  > You're saying that it's a good idea to change the comment char then?
Whoops.  My bad.  "!" is the line separator, not the comment character.

Sometimes I wonder if I'm going senile.

jeff

ps.  One can certainly argue about whether or not "!" is a good line
separator since it's also used in expression parsing and as a completer
for FP comparisons.  Basically we've got an ambiguous grammar due to some
poor choices that were made long ago ;(

jeff

  reply	other threads:[~2000-05-04  4:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200005040040.RAA14682@milano.cup.hp.com>
2000-05-04  0:49 ` [parisc-linux] crti.S Nested procedures error Alan Modra
2000-05-04  0:54   ` Jeffrey A Law
2000-05-04  1:27     ` Alan Modra
2000-05-04  4:45       ` Jeffrey A Law [this message]
2000-05-10 21:48 Cary Coutant
  -- strict thread matches above, loose matches on Subject: below --
2000-05-01 18:41 Grant Grundler
2000-05-03 14:18 ` Sam Creasey
2000-05-03 15:53   ` willy
2000-05-04  0:28     ` Alan Modra
2000-05-10 20:03 ` Paul Bame

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=27524.957415526@upchuck \
    --to=law@cygnus.com \
    --cc=alan@linuxcare.com.au \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.