Re: Overloading procedures with Float and Long_Float types

["Luke Guest" <lguest@bubball.com>]

"Preben Randhol" <randhol+abuse@pvv.org> wrote in message
news:mailman.77.1078762820.327.comp.lang.ada@ada-france.org...
> Luke Guest <lguest@bubball.com> wrote on 08/03/2004 (16:25) :
> > If I only provide one, the Long_Float/GLdouble variant, I'll either have
to
> > cast it down to GLfloat and use the fast function or use the slower
> > function. Not an option. It's designed that way for a reason.
>
> And the reason is? How does this work in C/C++ that doesn't even have

Not my bindings, the original C API of OpenGL.

> types...

It works, (again) by using distinct names.

> I think the design is flawed.
>
> Either it should be:
>
>    Translate_Double ( );
>
>    or
>
>    Double.Translate ( );

So, you would have GL.Double.Translate()?

Hmmm.