Re: Change of behavior for `define*'?

[Patrick McCarty]

On 2010-01-11, Andy Wingo wrote:
> On Mon 11 Jan 2010 03:48, Patrick McCarty <address@hidden> writes:
> 
> > With Guile 1.8.7, this code is valid:
> >
> >   guile> (use-modules (ice-9 optargs))
> >   guile> (define* a 1)
> >   guile> a
> >   1
> 
> Interesting, I wasn't aware of this. 

Thanks for the fix.

One other thing... I forgot that `define*-public' is still in (ice-9
optargs).  Guile 1.8 supports variable definitions for this construct
too:

  guile> (use-modules (ice-9 optargs))
  guile> (define*-public a 1)
  guile> a
  1

LilyPond uses (define*-public) like this occasionally, though most of
the time with procedures.

Thanks,
Patrick