From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: guile-emacs@sourceware.cygnus.com
Subject: Lisp reference to Scheme reference
Date: Mon, 01 May 2000 21:07:00 -0000 [thread overview]
Message-ID: <87og6pq5d6.fsf@PC486.Niemitalo.LAN> (raw)
My recent macro-importing changes have caused a problem.
Previously, imported macros always put the returned value through
`lispref->scm'. Now they make Lisp references just like imported
functions.
(define-module (emacs user)
:use-module (emacs import)
:use-module (emacs macro))
(begin-save-excursion 1)
=> #<procedure-with-setter>
I don't think we want a Lisp reference in this case. The easy
fix would be to make imported macros call `lispref->scm' again,
but that might be wrong for some macros. And it gets worse:
(define lr (object-property (begin-save-excursion 1)
'lisp-reference))
lr
=> #<lisp-reference>
(import-lisp-function prin1-to-string)
((prin1-to-string lr))
=> "#<scheme_reference>"
So we have a Lisp reference pointing to a Scheme reference.
I think make_lispref should return the original Scheme object
instead of making such double references. May I change it?
next reply other threads:[~2000-05-01 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-01 21:07 Kalle Olavi Niemitalo [this message]
2000-05-01 21:35 ` 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=87og6pq5d6.fsf@PC486.Niemitalo.LAN \
--to=tosi@stekt.oulu.fi \
--cc=guile-emacs@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).