[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Improve `seed->random-state' in stable-2.0?

From: Andy Wingo
Subject: Re: Improve `seed->random-state' in stable-2.0?
Date: Mon, 23 Jan 2012 15:06:23 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)

On Mon 23 Jan 2012 14:06, Mike Gran <address@hidden> writes:

>> From: Andy Wingo <address@hidden>
>>> (seed->random-state (current-time)) seems to be a common idiom that
>>> you would end up breaking.
>>This is a common idiom that is worth deprecating.  Mark's new functions
>>that seed the random state from /dev/urandom are much better.
> Are you suggesting that you'll break the API in the hope that when people's
> code stops working, they'll reread the manual and notice that
> random-state-from-platform exists?
> It seems a rather unfriendly way to accomplish that task.

That would indeed be a mean thing to do!  It's not what I'm suggesting
though.  Deprecation means causing Guile to emit warnings, at
compile-time or at runtime, indicating that a particular interface will
go away at some point, and noting the interface that should be used

I think it's fairly helpful, actually, but if you have any suggestions
for how it could be improved, they are much welcome.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]