Re: [AD] Allegro 4.2 todos

[Peter W. <tj...@al...>]

On 2003-06-03, Angelo <a.m...@li...> wrote:
> >> Humm, already commited a patch that makes the lib and all the
> >> programs/examples to use a private _al_rand()/_al_srand() interface.=
 Seems
> >> the best solution to me and also gives pretty good results here.
> >=20
> > This is blatantly contradictory: how can you make examples use a priv=
ate
> > function !???? Either it is private and you can't advertise it in exa=
mples,
> > or it is public and you can. No middle position.
>=20
> Humm, you're right. But then we're at the starting point again: we can'=
t
> have it private if we want it in the test program (as first case) and i=
n the
> other apps (examples, etc.). And if we make it public, how to call it?
> al_rand() comes to mind, but then it sounds like an al_ prefixed functi=
on in
> an unprefixed library and this is bad IMHO. rand_ex() could fit well en=
ough.
>=20
> Ideas?

Note that when I suggested the `private rand' idea, I only meant for it
to replace the uses of rand() in the dissolve blender.  This is a
separate problem from bad randomness in example programs.

As for the examples, is the bad randomness that bad?  I really have a
hard time believing that a libc rand() could be that useless.

BTW, thanks for doing the leg work for the first problem, Angelo.
--=20
=E7=8E=8B=E6=B5=A9=E7=A6=8E