9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] more extensions
Date: Tue, 16 Jul 2002 12:26:27 -0400	[thread overview]
Message-ID: <Pine.LNX.4.30.0207161225550.14125-100000@athena> (raw)
In-Reply-To: <3D3456EA.4B0BC1D4@gsyc.escet.urjc.es>

My next thought, but I figured I'd used all my contribution
credits today.

Sam

On Tue, 16 Jul
2002, FJ Ballesteros wrote:

>
> 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?
>



  reply	other threads:[~2002-07-16 16:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 16:08 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 15:31 ` Sam
2002-07-16 17:24 ` [9fans] more extensions FJ Ballesteros
2002-07-16 16:26   ` Sam [this message]
2002-07-16 17:28   ` Howard Trickey
2002-07-16 17:09     ` [9fans] New language? Sam
2002-07-17  5:45       ` GBA
2002-07-17  6:23         ` Lucio De Re
2002-07-16 18:23   ` [9fans] more extensions Scott Schwartz
2002-07-16 18:47     ` Dan Cross
2002-07-16 19:05       ` Jon Snader
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 18:44 rob pike, esq.
2002-07-17  8:58 ` Douglas A. Gwyn
     [not found] <nemo@gsyc.escet.urjc.es>
2001-10-09  6:25 ` [9fans] rewriting paths [was: mv vs cp] Fco.J.Ballesteros
2001-10-09  6:41   ` George Michaelson
2001-10-10  9:05     ` Douglas A. Gwyn
2001-10-09 14:19   ` Richard

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=Pine.LNX.4.30.0207161225550.14125-100000@athena \
    --to=sah@softcardsystems.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).