From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more extensions
Date: Tue, 16 Jul 2002 14:44:26 -0400 [thread overview]
Message-ID: <ea3d8aee92936501cfc2258e06aeee59@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
I love tuples, just love them, but I think C is not the place to
do language hacking any more. A case could even be made
that it wasn't the right place when Ken hacked it around 1988,
although a number of the changes were valuable and did make
it into the standard (e.g. indexed initializations).
-rob
[-- Attachment #2: Type: message/rfc822, Size: 2088 bytes --]
From: FJ Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] more extensions
Date: Tue, 16 Jul 2002 19:24:58 +0200
Message-ID: <3D3456EA.4B0BC1D4@gsyc.escet.urjc.es>
Including tuples (perhaps as an instance of nameless structs) would
simplify many interfaces, right? that's one thing I learned using
Limbo.
The extension would probably be not too complex, also.
I don't have time to implement this during this semester, but would
be willing to do so in the future if people from the Labs agree.
Is there agreement on this?
next reply other threads:[~2002-07-16 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 18:44 rob pike, esq. [this message]
2002-07-17 8:58 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 19:15 bwc
2002-07-16 19:46 ` Fariborz (Skip) Tavakkolian
2002-07-16 16:08 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 17:24 ` [9fans] more extensions FJ Ballesteros
2002-07-16 16:26 ` Sam
2002-07-16 17:28 ` Howard Trickey
2002-07-16 18:23 ` Scott Schwartz
2002-07-16 18:47 ` Dan Cross
2002-07-16 19:05 ` Jon Snader
2002-07-17 8:58 ` Douglas A. Gwyn
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=ea3d8aee92936501cfc2258e06aeee59@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).