unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bill Gribble <grib@linuxdevel.com>
Cc: guile-devel@gnu.org
Subject: Re: Parott
Date: 09 Nov 2002 09:49:53 -0600	[thread overview]
Message-ID: <1036856994.18084.89.camel@firetrap> (raw)
In-Reply-To: <200211090026.38817.clinton@unknownlamer.org>

On Fri, 2002-11-08 at 23:26, Clinton Ebadi wrote:
> I didn't finish my message, oops. Anyway, Parrot also has a working JIT 
> compiler among other things. Support for continuations is being worked on. 
> There is also a GC built in and big/exact number support too. It just seems 
> like a good idea to use Parrot. 

That sounds like a pretty good idea to me; it would be nice to get some
synergy from the Perl folks, and it seems like with a common bytecode
backend there could be some very nice interoperation potentials (i.e.
guile having a perl evaluator or some craziness like that).  Maybe this
is more of a practical direction to achieve the Guile dream of multiple
extension language syntaxes, too (not sure exactly how or if it relates,
but it seems like a possibility). 

b.g.




 




_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-11-09 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09  5:26 Parott Clinton Ebadi
2002-11-09 15:49 ` Bill Gribble [this message]
2002-11-10 19:40   ` Parott Jeff Read
2002-11-18 23:56 ` Parott Neil Jerram
2002-11-18 23:58 ` Parott Neil Jerram

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1036856994.18084.89.camel@firetrap \
    --to=grib@linuxdevel.com \
    --cc=guile-devel@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).