9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSOC proposal
Date: Sat, 17 Apr 2010 19:51:49 -0500	[thread overview]
Message-ID: <6923AD9A-6C0C-47E1-809F-067D8FA8527C@corpus-callosum.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

This is really too late for the GSoC bits.  But possibly of interests for later developments...


On Mar 25, 2010, at 6:03 AM, yy wrote:
> 
> 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.

A viable environment using in Plan 9 or Inferno to develop code for arrayForth and the GA line of chips that use it would be nice.  Well, nice for a few of us who may have future board designs using those chips.

Getting some Forth-SIM environment for any Plan 9 $objtype would help from having to run Windows IDEs on native x86 hardware or in VMs.  Additionally, flashing the GA chips from Plan 9 sure would make development decisions easier.

-jas


[-- Attachment #2: Type: text/html, Size: 1635 bytes --]

             reply	other threads:[~2010-04-18  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  0:51 Jeff Sickel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-28  2:19 Bruce Ellis
2010-03-25 11:03 ` yy

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=6923AD9A-6C0C-47E1-809F-067D8FA8527C@corpus-callosum.com \
    --to=jas@corpus-callosum.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).