From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Go
Date: Thu, 12 Nov 2009 12:13:50 -0500 [thread overview]
Message-ID: <316a7930366a66f13994b13161e339aa@ladd.quanstro.net> (raw)
In-Reply-To: <<9ab217670911120859u25b8f6f0m57cad5c126d75d65@mail.gmail.com>>
> Because it is constantly compared with C, C++, Java, and scripting
> languages. Its packages are sold as better than C header files, which
> is demonstrated in Russ' compile time video. It is a compiled language.
> Its syntax is not horribly divergent from C.
none of this line of reasoning bears on go's designer's
intentions. and i would be surprised (shocked actually)
if a vm were omitted for language positioning reasons,
rather than technical ones.
> It has support for pointers, so I guess so. I'd guess it's somewhat
> easier than C++, where you have to have an implementation for new
> before you can do much of anything else very C++-like. That said,
> it does have a language runtime like C++, so I suspect it does need
> some setup before some features (such as threads) can be used.
support for pointers isn't a requirement (cf: oberon).
also there are many things that a language can subtily make
writing a kernel in that language very difficult or impossible.
given that go has a runtime, it's reasonable to ask if the
runtime can be prevented from bothering interrupt routines
and other critical sections. (was this a problem with alef?)
- erik
next parent reply other threads:[~2009-11-12 17:13 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 [this message]
2009-11-12 17:29 ` LiteStar numnums
2009-11-12 18:40 ` Tharaneedharan Vilwanathan
[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=316a7930366a66f13994b13161e339aa@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).