unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: What is Guile?
Date: Wed, 3 Sep 2003 22:43:52 +0200	[thread overview]
Message-ID: <16214.21128.700682.727192@localhost.localdomain> (raw)
In-Reply-To: <200309021647.JAA27864@morrowfield.regexps.com>

lord@emf.net writes:
> [..interesting stuff elided..]

> For my part, shortly after Java was released, I demonstrated a C-like
> syntax for Guile.   I think that, quite bitrotted now, that code is
> still floating around.
> 
> Sure, a multi-lingual framework can, in some sense, use the set-union
> of all of those libraries.  On the other hand, the "styles" of various
> languages are sufficiently different that such library sharing is of
> distinctly limited utility.  A good Python library is not necessarily
> a good Scheme library or a good Java library or a good Tcl library.
> You can glue the libraries together in a pinch -- but to make a
> programming environment that is comprehensive yet compact and clean,
> you're probably better off sticking to just one programming language.
> 
> Nowadays, I don't think people care too much if you happen to be able
> to program Guile in Python.  (Evidence for this can be seen in the
> Real Soon Now translator for Python->Guile.)  Perhaps if
> Python-in-Guile offered significantly better performance or profoundly

It is interesting to note that Java is much more the "multi-lingual
framework", considering Kawa (Scheme in Java), Jython (Python in Java)
and host of other projects. (A colleague of mine had this neat
mini-Haskell-in-Java project.)  Apparently, the way to build such a
framework is by providing portable low-level byte-code operations,
glued to an extensive library.


-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl   |   http://www.xs4all.nl/~hanwen 


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


  reply	other threads:[~2003-09-03 20:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3EF2F7DF008213D5@pop3.es.tisadm.net>
2003-09-02 16:47 ` What is Guile? Tom Lord
2003-09-03 20:43   ` Han-Wen Nienhuys [this message]
2003-09-03 22:52     ` Tom Lord
2003-09-03 23:12       ` Han-Wen Nienhuys
2003-09-04  9:43   ` tomas
2003-10-07 17:11     ` Marius Vollmer
     [not found]   ` <3EF2E935008FB586@pop2.es.tisadm.net>
2003-09-07 22:22     ` Marius Vollmer
2003-09-02 18:08 ` What is Guile?y Thamer Al-Harbash
2003-09-03 16:34   ` Han-Wen Nienhuys
2003-09-02 21:03 ` What is Guile? Jonathan Bartlett
2003-09-02 21:59 ` Kevin Ryde
     [not found]   ` <3EF2F7DF008E4D8D@pop3.es.tisadm.net>
2003-09-07 12:38     ` Jeff Read
2003-09-08 17:14     ` Paul Jarc
2003-09-08 18:32       ` Thamer Al-Harbash
2003-09-08 21:39         ` Jonathan Bartlett
2003-09-09  0:33           ` Jeff Read
2003-09-09  2:43             ` Jonathan Bartlett
2003-09-09  3:25             ` Lynn Winebarger
2003-09-09 13:20             ` Dale P. Smith
2003-09-09 18:46             ` Andreas Rottmann
2003-09-10 11:55               ` Thamer Al-Harbash
2003-09-07 22:00 ` Marius Vollmer

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=16214.21128.700682.727192@localhost.localdomain \
    --to=hanwen@cs.uu.nl \
    --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).