From: skaller <skaller@users.sourceforge.net>
To: felix-language <felix-language@lists.sourceforge.net>
Cc: caml-list <caml-list@inria.fr>, will@exomi.com
Subject: Scheme added to Felix compiler
Date: 06 Nov 2004 11:54:14 +1100 [thread overview]
Message-ID: <1099702453.2496.101.camel@pelican.wigram> (raw)
I have just uploaded a revised tarball for Felix 1.0.18.
Felix is open source with BSD style FFAU licence.
http://felix.sf.net/downlooad/flx_1.0.18_src.tgz
This version now incorporates the Scheme interpreter
ocs-1.0 in the compiler. Ocs was
written by Ville-Pertti Keinonen <will@exomi.com>
and the original source can be obtained from
URL http://will.iki.fi/software/ocs/
A scheme reference can be found at
http://www.schemers.org/Documents/Standards/R5RS/HTML/
The interpreter is available standalone tool
(called 'ocs_main' at the moment, but the name will
probably change)
It can also be used with the Felix preprocessor.
#scheme (display "//generated by scheme\n")
#scheme (load "somefile.sch")
The environment is currently shared across
directives and include files so variables set
in one place can be used in subsequent places.
The #scheme directive is replaced by whatever it
writes to standard output, and is then
tokenised as if it were Felix code.
In future releases I may add system variables
and utilities to the environment, and perhaps
extend the interpreter so it can access some of
the compiler state. I will be examining whether
it is feasible to invert the control relation
of the front end so it's a scheme program
embedding Ocaml (rather than the other way arond).
This may help to make user control and extensions
easier to script.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
reply other threads:[~2004-11-06 0:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1099702453.2496.101.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=felix-language@lists.sourceforge.net \
--cc=will@exomi.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