Re: GUILE_WARN_DEPRECATED

[Steve Tell]

On Mon, 27 Dec 2004, Marius Vollmer wrote:

> David Pirotte <address@hidden> writes:
> 
> > but why is this so impossible to control behavior of a 'guile
> > variable' within guile itself? why guile isn't listening to my
> > setting? is this a module/environment limitation?
> 
> The reason is actually quite simple: guile only looks once at the
> environment variable, during initialization.  After that, you can not
> change the deprecation mode, which could be called a bug.

That fits - it does work to putenv() before calling scm_boot_guile or 
scm_init_guile().
I generally do:
        if (getenv("GUILE_WARN_DEPRECATED") == NULL)
                putenv("GUILE_WARN_DEPRECATED=no");

> I think I will add a debug option (to be set with 'debug-enable', say)
> that controls the deprecation mode.  Opinions?
 
Sounds like great idea to me.  
Developers of guile-using programs (should) care about 
deprecation-warnings, but their users often don't.

Steve