Re: Overloading procedures with Float and Long_Float types

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

"Preben Randhol" <randhol+valid_for_reply_from_news@pvv.org> wrote in
message
news:slrnc4ovhc.2eu.randhol+valid_for_reply_from_news@k-083152.nt.ntnu.no...
> On 2004-03-08, Luke Guest <lguest@bubball.com> wrote:
> >
> > Basically, it just seems to be wasting a good opportunity for
overloading
> > here.
>
> I really don't understand why one have a Float and a Long_Float in the
> first place? Why not simply have a Long_Float?

In OpenGL, there are a number of different ways to specify translations,
scales, vertices, normals, etc. GLfloat is normal single precision real
numbers, useful for games. GLdouble is useful for scientific visualisation.

Basically, it allows the programmer to pick which one to use. Games require
speed, so GLfloat is enough, scientific apps don't.

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.

Luke.