Re: Eval options macro: backward compatibility?

[Ludovic Courtès]

Hi,

Han-Wen Nienhuys <address@hidden> 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.