From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Emacs Lisp, macros
Date: Wed, 15 Jul 2009 00:15:28 +0200 [thread overview]
Message-ID: <874ote3o8v.fsf@gnu.org> (raw)
In-Reply-To: 4A5CE0F9.4080904@domob.eu
Hi Daniel!
Daniel Kraft <d@domob.eu> writes:
> yesterday and today I implemented lambda expressions and
> defvar/defconst/defun for elisp
Great news!
> as well as found a (hopefully good) solution to automatically create
> fluids not yet present on reference.
Is each Elisp variable mapped to a fluid? Eventually, you may need VM
instructions for fluid-{ref,set!}, to speed things up.
[...]
> Regarding the test-suite: It seems to me there's no 'very extensive'
> and 'complete' single test-suite for guile at the moment, but I might
> be mistaken. So maybe I should create testsuite/elisp and a
> run-elisp-tests.scm like the one for vm which loads/compiles/runs and
> all that the individual tests? Or is there some existing framework I
> can plug my tests into?
There's 1.5 framework. The first one is under `test-suite/tests', used
to test the API. The remaining 0.5 is under `testsuite': it's inherited
from Guile-VM and is used to make sure interpreted and compiled code
yield the same result.
I think the best way would be to add, say,
`test-suite/tests/elisp-compiler.test' (there's already `elisp.test'),
and from there use a macro akin to Andy's `c&e' in `bytevectors.test'.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-07-14 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 19:48 Emacs Lisp, macros Daniel Kraft
2009-07-14 22:15 ` Ludovic Courtès [this message]
2009-07-15 8:36 ` Daniel Kraft
2009-07-23 22:14 ` Andy Wingo
2009-07-24 7:00 ` Daniel Kraft
2009-07-23 22:09 ` Andy Wingo
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=874ote3o8v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).