Re: naming scheme for the GSL package

[ederag]

On Thursday, October 20, 2016 08:34:10 Julien Bect wrote:
> Ok.  I will go for the full gsl functions names, then.
> 
> I wonder if there is a clever way to create function aliases in Octave : 
> for instance, to have both "clausen" and "gsl_sf_clausen" call the same 
> function.
> 
> If not, I will simply create duplicates of the functions that were there 
> in the 1.08 release during bootstrap.
> 
> Any ideas ?

For lack of better idea,
put wrappers with old names,
in a separate directory, with a command like
"gsl_without_gsl_sf_prefix(boolean)" 
that removes or adds this directory to path ?

The first "pkg load gsl", 
should issue  gsl_without_gsl_sf_prefix(true)
(for backward compatibility)
with a deprecation warning.

The user might then prefer to set
gsl_without_gsl_sf_prefix(false)
to get the gsl_sf_* naming scheme.