From: Al Viro <viro@ftp.linux.org.uk>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Michael Stefaniuc <mstefani@redhat.com>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: '$' as "valid" character in identifiers
Date: Thu, 24 May 2007 15:10:15 +0100 [thread overview]
Message-ID: <20070524141015.GG4095@ftp.linux.org.uk> (raw)
In-Reply-To: <46559093.5060908@knosof.co.uk>
On Thu, May 24, 2007 at 02:18:11PM +0100, Derek M Jones wrote:
> Al,
>
> >And now for reality: of course if we set out to imitate the implementation
> >allowing $, we'd better imitate it. The question is what to watch out
> >for and how to avoid buggering the tokenizer in process.
>
> If sparse is going to imitate a VAX implementation then how $ is glued
> is probably the least of the implemention worries.
I suspect that the real issue is whatever stuff Windows uses (and no,
I don't have Windows boxen either). Anybody who wants to work on
code that last compiled on VAX is not going to be happy with what
sparse will say about it, anyway. More realistic case is a codebase
with some VMS ancestry that got moved to Windows.
next prev parent reply other threads:[~2007-05-24 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 21:43 '$' as "valid" character in identifiers Michael Stefaniuc
2007-05-23 22:00 ` Michael Stefaniuc
2007-05-23 22:10 ` Linus Torvalds
2007-05-24 10:04 ` Al Viro
2007-05-24 11:14 ` Derek M Jones
2007-05-24 12:35 ` Al Viro
2007-05-24 13:18 ` Derek M Jones
2007-05-24 14:10 ` Al Viro [this message]
2007-05-24 14:43 ` Derek M Jones
2007-05-24 14:50 ` Michael Stefaniuc
2007-05-24 14:26 ` Neil Booth
2007-05-24 14:35 ` Neil Booth
2007-05-24 14:36 ` Neil Booth
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=20070524141015.GG4095@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=derek@knosof.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=mstefani@redhat.com \
--cc=torvalds@linux-foundation.org \
/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 NNTP newsgroup(s).