From: Hans Aberg <haberg-1@telia.com>
To: guile-user@gnu.org
Subject: Functional language syntax
Date: Wed, 22 Dec 2010 12:30:55 +0100 [thread overview]
Message-ID: <5589DD89-265A-439B-B611-55D784AC6396@telia.com> (raw)
I have put up the source code of the standard functional language
syntax program on top of Guile mentioned in earlier posts. One can see
that Guile already has a combined imperative/functional syntax, but to
go further, it would need to be extended.
Take down the file guile++.tar.bz2 inside the folder on the webpage
below, unpack using 'tar -xjf'; inside there is a file Readme.txt with
further instructions and examples. It is possible to pretty-print as
Scheme code, so it should be easy to see what the program does.
Hans
https://www-lagring.telia.se/Shares/Home.aspx?ShareID=e195dec2-1c1a-42a1-851e-da47e674d91b
next reply other threads:[~2010-12-22 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:30 Hans Aberg [this message]
2010-12-22 21:12 ` Functional language syntax Linas Vepstas
2010-12-22 21:23 ` Hans Aberg
2011-01-04 16:51 ` Ludovic Courtès
2011-01-04 19:39 ` Hans Aberg
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=5589DD89-265A-439B-B611-55D784AC6396@telia.com \
--to=haberg-1@telia.com \
--cc=guile-user@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).