From: Tharaneedharan Vilwanathan <vdharani@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go
Date: Thu, 12 Nov 2009 10:40:39 -0800 [thread overview]
Message-ID: <dac0a5820911121040v4888fe29g119dc746dfb39388@mail.gmail.com> (raw)
In-Reply-To: <316a7930366a66f13994b13161e339aa@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
>
> and other critical sections. (was this a problem with alef?)
as far as i know, not many alef programs were written. the few that were
written (like acme) got converted to C. and i dont think alef was used for
writing kernel code.
someone please correct me if i am wrong.
thanks
dharani
[-- Attachment #2: Type: text/html, Size: 522 bytes --]
next prev parent reply other threads:[~2009-11-12 18:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<9ab217670911120859u25b8f6f0m57cad5c126d75d65@mail.gmail.com>
2009-11-12 17:13 ` erik quanstrom
2009-11-12 17:29 ` LiteStar numnums
2009-11-12 18:40 ` Tharaneedharan Vilwanathan [this message]
[not found] <<9ab217670911120728q137ac2c1j4f11d9a1d8b2ded5@mail.gmail.com>
2009-11-12 16:37 ` erik quanstrom
2009-11-12 16:59 ` Devon H. O'Dell
2009-11-12 18:49 ` Roman Shaposhnik
2009-11-12 4:31 Nick LaForge
2009-11-12 5:27 ` Roman Shaposhnik
2009-11-12 15:28 ` Devon H. O'Dell
2009-11-12 20:51 ` Nick LaForge
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 6:00 Russ Cox
2009-11-11 6:33 ` Anant Narayanan
2009-11-11 6:47 ` Skip Tavakkolian
2009-11-11 11:27 ` Eris Discordia
[not found] ` <D67AC32CFE1076880E2CDDD5@192.168.1.2>
2009-11-11 16:25 ` John Waters
2009-11-11 17:23 ` roger peppe
2009-11-11 7:25 ` Roman Shaposhnik
2009-11-11 17:23 ` Russ Cox
2009-11-12 5:08 ` andrey mirtchovski
2009-11-12 5:25 ` Russ Cox
2009-11-12 5:46 ` Jeff Sickel
2009-11-12 6:39 ` Russ Cox
2009-11-12 16:37 ` Michaelian Ennis
2009-11-12 17:09 ` AngryDude
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=dac0a5820911121040v4888fe29g119dc746dfb39388@mail.gmail.com \
--to=vdharani@gmail.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).