From: yy <yiyu.jgl@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: plan9-gsoc@googlegroups.com
Subject: Re: [9fans] GSOC proposal
Date: Thu, 25 Mar 2010 12:03:17 +0100 [thread overview]
Message-ID: <a81fe9be1003250403q21a8e87dvcd48e30780da238b@mail.gmail.com> (raw)
In-Reply-To: <775b8d190903271919s2edd19o50566c14c37a3453@mail.gmail.com>
2009/3/28 Bruce Ellis <bruce.ellis@gmail.com>:
> Just a suggestion,
>
> A good forth system using acme, probably based on fgb's 4th. The goal
> is to conquer the Seaforth chip.
>
> I know the dev kit is US$500 but their compiler and simulator, written
> in forth, doesn't need hardware.
>
> And at least two 9fans have a kit.
>
> brucee
>
>
Would such a project be interesting for this year gsoc? Is any mentor
interested in Forth?
I really think acme would make a great environment for Forth
development. I have not used 4th except to play a bit with it, but I
have spent the last months porting the Ngaro VM to Go [1], which is
used to run retroForth [2] images, and I think that could be a good
starting point too.
[1] http://hg.4l77.com/gonga/
[2] http://retroforth.org
PS: I'm CCing this to the GSoC list, but since the original message
appeared here I'm replying to 9fans too.
--
- yiyus || JGL . 4l77.com
--
You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code" group.
To post to this group, send email to plan9-gsoc@googlegroups.com.
To unsubscribe from this group, send email to plan9-gsoc+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/plan9-gsoc?hl=en.
next prev parent reply other threads:[~2010-03-25 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 2:19 Bruce Ellis
2010-03-25 11:03 ` yy [this message]
2010-04-18 0:51 Jeff Sickel
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=a81fe9be1003250403q21a8e87dvcd48e30780da238b@mail.gmail.com \
--to=yiyu.jgl@gmail.com \
--cc=9fans@9fans.net \
--cc=plan9-gsoc@googlegroups.com \
/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).