unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jonathan Bartlett <johnnyb@eskimo.com>
Subject: Ideas
Date: Fri, 23 May 2003 15:18:49 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSU.4.44.0305231511330.22385-100000@eskimo.com> (raw)

I'm new to the list.  Here are some ideas that I have thought about
implementing if I have the time, but I thought I'd share them here in case
I'm way off-base.

1) A Guile dump()-type function

In order to get compile-time evaluation / run-time evaluation separation,
as well as to make executables work without the GUILE runtime, I was
thinking about implementing a dump/undump mechanism for GUILE.

Basically, have a procedure called (end-compile-time-evaluation)
which would do the following:

  * Save the current continuation in a variable
  * Set a global variable restart_from_continuation
  * call dump()

Then, it would be undumped into a regular executable.  The only change to
guile itself would be to check the restart_from_continuation variable when
starting and call the continuation if it is not null.

This would give the following advantages:

  * Guile would not have to be distributed w/ the app
  * Apps wouldn't have to wait for modules to load before starting, if
they load them before calling (end-compile-time-evaluation)
  * No initialization would be necessary
  * You can do real compile-time programming.

Anyway, it's something I've been thinking about working on, let me know if
I'm wrong-headed or someone has a better idea.

Jon




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


             reply	other threads:[~2003-05-23 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 22:18 Jonathan Bartlett [this message]
2003-06-01 21:18 ` Ideas Marius Vollmer
2003-06-01 21:46   ` Ideas Jonathan Bartlett

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=Pine.GSU.4.44.0305231511330.22385-100000@eskimo.com \
    --to=johnnyb@eskimo.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).