Re: complex number API

[Brian Gough <bjg@netsci.freeserve.co.uk>]

I generally use _t if the type is a single element, like an unsigned int
or function pointer, and drop the _t for a struct/class (e.g. like
time_t vs struct tm).  gsl_complex_t seems wrong to me somehow.

Mark Galassi wrote:
> 
>     James> By the way, I'm not necessarily advocating this for gsl,
>     James> but i noticed on another project if i named all my new data
>     James> types things that ended in _t, eg "Complex_t", then emacs
>     James> would color them as if they were builtin types.  it also
>     James> made it a little easier to avoid confusion about variable
>     James> names and type names.
> 
> that is a very nice idea, and if we are slowing down the API evolution
> with 0.4.x we should consider this.
> 
> One shortcoming I see is that gsl_complex_t is longer.
> 
> complex_t is better, but might conflict with other code.  Of course
> some day gsl will be the only source of numerical routines, so maybe
> that doesn't matter :-)