Re: [AD] Allegro 4.2 todos

[Peter Wang <tjaden@xxxxxxxxxx>]

On 2003-06-03, Angelo <a.mottola@xxxxxxxxxx> 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.
> > 
> > This is blatantly contradictory: how can you make examples use a private
> > function !???? Either it is private and you can't advertise it in examples,
> > or it is public and you can. No middle position.
> 
> 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 in 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 function in
> an unprefixed library and this is bad IMHO. rand_ex() could fit well enough.
> 
> 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.
-- 
王浩禎