From: Zack Weinberg <zack@codesourcery.com>
To: Matt Austern <austern@apple.com>
Cc: gcc@gcc.gnu.org, Per Bothner <per@bothner.com>,
"Joseph S. Myers" <jsm@polyomino.org.uk>
Subject: Re: #pragma interface/implementation broken if --enable-mapped-location
Date: Wed, 29 Sep 2004 22:50:00 -0000 [thread overview]
Message-ID: <871xgkuci2.fsf@codesourcery.com> (raw)
In-Reply-To: <837EF2C2-1247-11D9-AE93-000393B2ABA2@apple.com> (Matt Austern's message of "Wed, 29 Sep 2004 11:43:54 -0700")
Matt Austern <austern@apple.com> writes:
>> I think we're at least a couple weeks away from #pragma-as-tokens. A
>> quickie fix would be fine by me.
>
> The reason I didn't implement pragma-as-tokens was pretty simple:
> I thought it would involve fairly tricky changes in both libcpp and
> the front end.
>
> First, the libcpp changes: it's easy to get libcpp to do parsing
> the same way it normally does but using a different source of
> characters; the infrastructure is already there. I didn't see an
> easy way of getting the pragma handlers to use an alternate
> mechanism for getting tokens. There is no such infrastructure in
> the existing libcpp, and creating something new, just for this
> purpose, didn't seem worth it.
The way I have in mind for #pragma-as-tokens, hardly any changes to
cpplib should be necessary at all.
I think you'll like what I wind up implementing. It's three or four
patches down the road, though; let's not worry about it now.
zw
next prev parent reply other threads:[~2004-09-29 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:08 Per Bothner
2004-09-24 2:22 ` Zack Weinberg
2004-09-24 2:43 ` Per Bothner
2004-09-24 4:58 ` Zack Weinberg
2004-09-24 14:17 ` Joseph S. Myers
2004-09-24 21:47 ` Zack Weinberg
2004-09-24 22:15 ` Joseph S. Myers
2004-09-24 22:34 ` Zack Weinberg
2004-09-29 19:24 ` Per Bothner
2004-09-29 20:56 ` Zack Weinberg
2004-09-29 21:57 ` Matt Austern
2004-09-29 22:50 ` Zack Weinberg [this message]
2004-09-30 7:57 ` Per Bothner
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=871xgkuci2.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=austern@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
--cc=per@bothner.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).