unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
To: linasvepstas@gmail.com
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile history: your input needed!
Date: Sun, 23 Nov 2008 20:17:55 -0500	[thread overview]
Message-ID: <87ljv9c470.fsf@unknownlamer.org> (raw)
In-Reply-To: <3ae3aa420811230840x61d4778fh2c2c9d6122eb25b6@mail.gmail.com> (Linas Vepstas's message of "Sun, 23 Nov 2008 10:40:59 -0600")

"Linas Vepstas" <linasvepstas@gmail.com> writes:

> Hi,
>
> 2008/11/23 Neil Jerram <neiljerram@googlemail.com>:
>>  If we had a clearer statement of
>> the present, it would not matter so much how people describe the past.
>
> Is there a clear expression of a vision for the future?
> What might one look forward to? What needs to be
> done?

In the near future it looks like the task list is something like:

 * Merge the guile-vm branch into trunk
 * Ditch the Guile GC for BDW-GC (maybe; the lower latencies and
   parallel collector give it a clear advantage of the Guile GC IMO)
 * Unicode string support (perhaps for the first post stable-guile-vm
   release).
 * CFFIesque runtime loading of foreign functions

A 2.0 release with at least guile-vm would be nice (perhaps six months
or so from now?); the C API has stabilized nicely over the last few
years, and so it is now much easier to write extensions that won't
bitrot--it is not so difficult to write something that will work with
1.6->git-head (there used to be a lot more libraries for Guile; most of
them were written in the 1.3/4 days and are severely incompatible with
modern Guile).

After guile-vm is mainline it would be nice if Guile really became the
GNU Ubiquitous Intelligent Language for Extension. Finding GNU programs
that could use an extension language and embedding Guile, replacing
existing application specific scripting languages with FOO->Guile
translators, and binding useful GNU libraries should be done to as many
GNU projects as possible.

In the long long term the guile-vm compiler framework could be used to
translate other languages into Scheme (or GHIL/GLIL/vm-bytecode)
fufilling one of the original goals of Guile (embed Guile in your
application and now end users can use whatever language they please to
write extensions--with some interoperability between them). A good early
language to write a translator for would be ECMAScript; no one expects
consistency between embedded ES systems and the standard library is
small enough to implement quickly in Scheme.

In the u256_t term replacing the Emacs interpreter with Guile and an
elisp->{scheme/GHIL/GLIL/...} translator.

-- 
                     How can you accept social supression                      
                      This weak state of mind in our time                      
                        I demand release from hypocrisy                        
                 I'd rather die than be held down, forced down                 




  reply	other threads:[~2008-11-24  1:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 20:00 guile history: your input needed! Andy Wingo
2008-11-21  0:34 ` Neil Jerram
2008-11-21  4:21   ` Sebastian Tennant
2008-11-23  9:40     ` Neil Jerram
2008-11-23 12:32       ` Andy Wingo
2008-11-21 11:36   ` Andy Wingo
2008-11-23 10:04     ` Neil Jerram
2008-11-23 16:40       ` Linas Vepstas
2008-11-24  1:17         ` Clinton Ebadi [this message]
2008-11-22 22:46   ` Keith Wright
2008-11-23 10:56     ` Neil Jerram
2008-11-23 12:24     ` Ludovic Courtès

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=87ljv9c470.fsf@unknownlamer.org \
    --to=clinton@unknownlamer.org \
    --cc=guile-user@gnu.org \
    --cc=linasvepstas@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).