This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Unwanted hook names (was Re: interface reductions)
- To: Ian Grant <Ian dot Grant at cl dot cam dot ac dot uk>
- Subject: Re: Unwanted hook names (was Re: interface reductions)
- From: cwitty at newtonlabs dot com (Carl R. Witty)
- Date: 30 May 2000 13:35:44 -0700
- Cc: Dirk Herrmann <dirk at ida dot ing dot tu-bs dot de>, Guile Mailing List <guile at sourceware dot cygnus dot com>
- References: <E12wKU3-0005xA-00@wisbech.cl.cam.ac.uk>
Ian Grant <Ian.Grant@cl.cam.ac.uk> writes:
> dirk@ida.ing.tu-bs.de said:
> > So I have to agree with you that this is extremely bad. But, the only
> > way we could cause a compile time error would be to either rename
> > scm_create_hook or change it's parameter list.
>
> > So, what to do about this problem: It's not too bad of an idea to say
> > that functions with changing behaviour get renamed. But, if the name
> > was quite allright, you wouldn't like to do this. And, you change
> > something again, and the next release you change the name back again.
> > Hmmm?
>
> What about using #error and #warning preprocessor directives, or are these GNU
> specific?
I don't see how to use #error to give errors if you use a deprecated
function.
Carl Witty