From: ludo@chbouib.org (Ludovic Courtès)
Subject: Re: Eval options macro: backward compatibility?
Date: Sat, 20 Jan 2007 15:35:18 +0100 [thread overview]
Message-ID: <871wlprck9.fsf@chbouib.org> (raw)
In-Reply-To: eoqnqp$ki1$1@sea.gmane.org
Hi,
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> this order is awkward when a new trap option has to be added.
>
> The problematic thing is that this is exported to GUILE users, through
>
> #define SCM_ENTER_FRAME_P scm_evaluator_trap_table[1].val
>
> in eval.h
>
> I would like to change this order, and if possible move this out of
> the global namespace. Are there any objections?
It's ok for 1.9 to break binary compatibility, and it's also probably a
good thing to not export things that are not documented. So I think
SCM_EVALUATOR_TRAP_TABLE could either be made `static' or renamed to
SCM_I_..., and `SCM_ENTER_FRAME_P' could certainly be moved in `eval.c'
if it's not needed elsewhere.
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-20 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 15:24 Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-20 14:35 ` Ludovic Courtès [this message]
2007-01-22 14:18 ` Han-Wen Nienhuys
2007-01-22 20:48 ` Kevin Ryde
2007-01-23 0:51 ` deprecated features Han-Wen Nienhuys
2007-01-23 1:03 ` Kevin Ryde
2007-01-23 1:20 ` Han-Wen Nienhuys
2007-01-23 14:50 ` Bruce Korb
2007-01-23 22:45 ` Han-Wen Nienhuys
2007-01-23 23:20 ` Bruce Korb
2007-01-24 0:44 ` Han-Wen Nienhuys
2007-01-24 0:10 ` Bruce Korb
2007-01-23 23:10 ` Han-Wen Nienhuys
2007-01-23 23:35 ` Bruce Korb
2007-01-24 0:38 ` Han-Wen Nienhuys
2007-01-24 22:44 ` Kevin Ryde
2007-01-22 15:28 ` Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-22 20:50 ` Kevin Ryde
2007-01-24 21:05 ` Kevin Ryde
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=871wlprck9.fsf@chbouib.org \
--to=ludo@chbouib.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).