From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] s_putc and Runes
Date: Mon, 5 Feb 2007 13:42:02 -0800 [thread overview]
Message-ID: <9F6E7B05-89E8-4844-BFAF-0616C36DF910@telus.net> (raw)
In-Reply-To: <0dd26eea2ab28ef6f63e027c70ed8630@plan9.jp>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5-Feb-07, at 11:52 AM, Joel Salomon wrote:
> Maybe if someone needs/wants to implement a language
> with a built-in string type…
That's crazy-talk.
;-)
Paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFx6SrpJeHo/Fbu1wRAhGnAKCPibBrE9WPP38TT7aV9cbFyoxOKACfe68A
DfPmHYkqeDPGx5Z0HukrtGg=
=s/8V
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-02-05 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 2:41 Joel Salomon
2007-02-05 3:25 ` Russ Cox
2007-02-05 9:41 ` Bruce Ellis
2007-02-05 12:25 ` erik quanstrom
2007-02-05 19:52 ` Joel Salomon
2007-02-05 21:42 ` Paul Lalonde [this message]
2007-02-05 23:57 ` Joel Salomon
2007-02-06 6:23 ` Bruce Ellis
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=9F6E7B05-89E8-4844-BFAF-0616C36DF910@telus.net \
--to=plalonde@telus.net \
--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).