From: "Dennis Ritchie" <dmr@bell-labs.com>
To: 9fans@9fans.net
Subject: Re: [9fans] hoc's behaviour, unary operators
Date: Mon, 2 Nov 2009 09:56:17 +0000 [thread overview]
Message-ID: <7l1oq8F3c4ieqU1@mid.individual.net> (raw)
In-Reply-To: <332ccdbfcadf7769acbbd00931f5cde4@brasstown.quanstro.net>
"erik quanstrom" <quanstro@quanstro.net> wrote in message
news:332ccdbfcadf7769acbbd00931f5cde4@brasstown.quanstro.net...
...
> therefore the string "a++b" can't be valid, since the tokens
> the parser sees are "a" INC "b". that's not kosher c. way
> back when in primoridal c, there were no seperate tokens
> for INC and DEC, they were productions in the parser and
> goofiness like you describe was allowed.
No, in fact even in primordial C ++ -- were indeed separate tokens.
However, in several early versions =+ and =- [sic] etc. were
two tokens each, then adjoined by the parser.
Dennis
next prev parent reply other threads:[~2009-11-02 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<a560a5d00910301119t4ee76736j80bdebbb9fa9bd31@mail.gmail.com>
2009-10-30 18:28 ` erik quanstrom
2009-10-30 19:03 ` matt
2009-10-30 19:39 ` Rudolf Sykora
2009-11-02 9:56 ` Dennis Ritchie [this message]
2009-10-30 15:20 Rudolf Sykora
2009-10-30 15:44 ` Rudolf Sykora
2009-10-30 15:55 ` Jorden Mauro
2009-10-30 16:09 ` Rudolf Sykora
2009-10-30 16:27 ` Martin Neubauer
2009-10-30 18:19 ` Rudolf Sykora
2009-10-30 16:22 ` Martin Neubauer
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=7l1oq8F3c4ieqU1@mid.individual.net \
--to=dmr@bell-labs.com \
--cc=9fans@9fans.net \
/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).