From: Richard Earnshaw <Richard.Earnshaw@arm.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
hp@bitrange.com, schwab@suse.de, binutils@sources.redhat.com,
Philip Blundell <pb@nexus.co.uk>
Subject: Re: demand_empty_rest_of_line and ignore_rest_of_line
Date: Tue, 27 Apr 2004 11:43:00 -0000 [thread overview]
Message-ID: <1083063340.14083.34.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <m3d65u3x99.fsf@gossamer.airs.com>
On Tue, 2004-04-27 at 04:39, Ian Lance Taylor wrote:
> You left
> out the truly dreadful ARM .symver, in which '@' starts a comment at
> any time--except when it appears in the operand of .symver. And,
> repeating myself, MRI mode.
I'd dearly like to deprecate use of '@' as a comment char, but it's not
trivial. There simply is no single char in ASCII (with the possible
exception of '`') that can be used as a substitute and that doesn't have
other uses in the syntax.
One possibility would be to adopt a 2-character sequence (such as '//'),
and to that extent I notice that there is already code in the parser to
handle this.
However, there's still the legacy issue. Old versions of gcc generate @
in abundance, and there is substantial hand-written assembly code out
there that does similarly. One way of addressing this might be to
reject '@' in the EABI conforming modes -- it provides a relatively
clean cut-off point. Can the selection of comment characters be made
command-line option dependent?
R.
next prev parent reply other threads:[~2004-04-27 10:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 16:36 Nathan Sidwell
2004-03-17 16:43 ` Hans-Peter Nilsson
2004-03-17 16:49 ` Ian Lance Taylor
2004-03-18 10:29 ` Nathan Sidwell
2004-03-18 13:15 ` Ian Lance Taylor
2004-04-23 23:15 ` Andreas Schwab
2004-04-24 17:36 ` Hans-Peter Nilsson
2004-04-24 17:57 ` Andreas Schwab
2004-04-24 18:26 ` Hans-Peter Nilsson
2004-04-24 19:22 ` Andreas Schwab
2004-04-24 21:31 ` Hans-Peter Nilsson
2004-04-24 21:33 ` Andreas Schwab
2004-04-24 23:25 ` Hans-Peter Nilsson
2004-04-24 23:37 ` Andreas Schwab
2004-04-25 0:03 ` Zack Weinberg
2004-04-25 0:22 ` Hans-Peter Nilsson
2004-04-26 0:28 ` Zack Weinberg
2004-04-26 0:58 ` Hans-Peter Nilsson
2004-04-26 2:14 ` Hans-Peter Nilsson
2004-04-25 23:35 ` Ian Lance Taylor
2004-04-26 0:51 ` Zack Weinberg
2004-04-26 2:46 ` Ian Lance Taylor
2004-04-26 3:13 ` Zack Weinberg
2004-04-26 14:16 ` Ian Lance Taylor
2004-04-26 14:22 ` Andreas Schwab
2004-04-26 14:34 ` Richard Earnshaw
2004-04-26 15:29 ` Ian Lance Taylor
2004-04-26 19:26 ` Hans-Peter Nilsson
2004-04-26 19:42 ` Kai Henningsen
2004-04-26 19:45 ` Ian Lance Taylor
2004-04-26 20:04 ` Ian Lance Taylor
2004-04-27 1:32 ` Zack Weinberg
2004-04-27 2:02 ` Hans-Peter Nilsson
2004-04-27 2:38 ` Zack Weinberg
2004-04-27 2:35 ` Alan Modra
2004-04-27 3:13 ` Zack Weinberg
2004-04-27 4:33 ` Ian Lance Taylor
2004-04-27 5:19 ` Zack Weinberg
2004-04-27 6:52 ` Ian Lance Taylor
2004-04-27 11:43 ` Richard Earnshaw [this message]
2004-04-27 2:47 ` Ian Lance Taylor
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=1083063340.14083.34.camel@pc960.cambridge.arm.com \
--to=richard.earnshaw@arm.com \
--cc=binutils@sources.redhat.com \
--cc=hp@bitrange.com \
--cc=ian@wasabisystems.com \
--cc=pb@nexus.co.uk \
--cc=schwab@suse.de \
--cc=zack@codesourcery.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).