public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: Keisuke Nishida <kxn30@po.cwru.edu>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: special forms (save-excursion)
Date: Wed, 15 Mar 2000 11:30:00 -0000	[thread overview]
Message-ID: <874sa8azw4.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <m33dpsl56b.fsf@kei.cwru.edu>

Keisuke Nishida <kxn30@po.cwru.edu> writes:

> Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:
> 
> > Should I use defmacro instead of syntax-rules?  I like
> > syntax-rules more, but it seems slower.
> 
> I think faster one is better.  This is not a complex syntax and
> easy to maintain.

But the macros made with define-macro (what is the difference
between that and defmacro?) are not hygienic by default.  Should
we hygienize each of them separately, or do we just give people a
list of symbols which they must not rebind when using the macros?

> (define-public (lisp-false? sexp) (or (eq? sexp ()) (eq? sexp nil)))

R5RS doesn't say what () evaluates to, so it would be better to
quote it.

I believe "sexp" means the usual printed form of an expression.
The parameter of lisp-false? is the object itself, not a printed
form.  Use "obj" instead.

> (define-public (lisp-variable-set! symbol value)
>   (lisp-eval `(setq ,symbol ,value)))

The value should be quoted in the setq call.

(define-public (lisp-variable-set! symbol value)
  (lisp-eval `(setq ,symbol ',value)))

> (define-macro (import-lisp-variable-1 variable . rest)
>   (let ((name (if (pair? rest) (car rest) variable)))
>     `(define ,name (make-procedure-with-setter
> 		    (lambda () (lisp-variable-ref ',variable))
> 		    (lambda (value) (lisp-variable-set! ',variable value))))))
> (define-public import-lisp-variable import-lisp-variable-1)

Can't you just (export import-lisp-variable-1)?

  parent reply	other threads:[~2000-03-15 11:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-14 12:46 Kalle Olavi Niemitalo
2000-03-14 13:32 ` Keisuke Nishida
2000-03-14 14:11 ` Keisuke Nishida
2000-03-14 14:17   ` Keisuke Nishida
2000-03-15  0:34   ` Kalle Olavi Niemitalo
2000-03-15  3:32     ` Keisuke Nishida
2000-03-15  5:11       ` Kalle Olavi Niemitalo
2000-03-15  5:43         ` Keisuke Nishida
2000-03-15  6:12           ` Kalle Olavi Niemitalo
2000-03-15 11:37             ` guile-emacs GC (was special forms) Kalle Olavi Niemitalo
2000-03-15 12:18               ` Keisuke Nishida
2000-03-15 13:48                 ` Jim Blandy
2000-03-15 15:14                   ` Keisuke Nishida
2000-03-15 11:30           ` Kalle Olavi Niemitalo [this message]
2000-03-15 12:42             ` special forms (save-excursion) Keisuke Nishida

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=874sa8azw4.fsf@PC486.Niemitalo.LAN \
    --to=tosi@stekt.oulu.fi \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=kxn30@po.cwru.edu \
    /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).