From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: rm@fabula.de, guile-devel@gnu.org
Subject: Re: scm_* API extension? [was] scm_* API question
Date: Mon, 5 Aug 2002 20:12:27 +0200 [thread overview]
Message-ID: <15694.49163.715320.366211@meddo.cs.uu.nl> (raw)
In-Reply-To: <ljn0s1fb3k.fsf@burns.dt.e-technik.uni-dortmund.de>
marius.vollmer@uni-dortmund.de writes:
>
> What is an 'interpreter'? What do multiple instances of the
> interpreter have in common, what is specific to each instance? I
> think that once you know what you want from multiple interpreters, you
> can implement them easily with the features we already have. Or with
> fork.
What I want is a way to encapsulate state changes; modules give a nice
way to deal with naming variables, but not with their values. When I
have two lilypond files, one doing
f1.ly
#(set! global-foo-option #t) ;; default = #f
\score {\notes { .. } }
f2.ly
\score { \notes { ..other notes.. } }
What really happens during execution depends on the order of
execution: if you do
lilypond f1 f2
then f2 is processed with global-foo-option set to #t. If you change
the order, then f2 is processed with global-foo-option set to #f.
It would be nice if we could have some kind of copy-on-write system
for variables, so that I can reset the state of the variables before
processing each new file.
[disclaimer, I know nothing of advanced Scheme techniques, I might be
missing some basic idiom here completely.]
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-05 18:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 12:14 scm_* API question rm
2002-07-31 1:09 ` Christopher Cramer
2002-07-31 10:03 ` scm_* API extension? [was] " rm
2002-07-31 10:10 ` Marius Vollmer
2002-07-31 18:21 ` rm
2002-07-31 21:59 ` Rob Browning
2002-08-01 10:10 ` rm
2002-08-01 16:51 ` Rob Browning
2002-08-05 15:08 ` Marius Vollmer
2002-08-05 16:06 ` rm
2002-08-05 16:49 ` Marius Vollmer
2002-07-31 20:06 ` Christopher Cramer
2002-07-31 22:14 ` Rob Browning
2002-08-01 9:41 ` rm
2002-08-05 17:51 ` Marius Vollmer
2002-08-05 18:12 ` Han-Wen Nienhuys [this message]
2002-08-05 18:45 ` Rob Browning
2002-08-05 18:31 ` Rob Browning
2002-08-05 18:33 ` rm
2002-08-05 15:12 ` Marius Vollmer
2002-07-31 10:11 ` Marius Vollmer
2002-07-31 10:30 ` rm
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=15694.49163.715320.366211@meddo.cs.uu.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@gnu.org \
--cc=rm@fabula.de \
/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).