[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-commits
Subject:    Re: [PATCH] libc++: add NaCl and PNaCl support for std::random_device
From:       JF Bastien <jfb () chromium ! org>
Date:       2014-11-27 23:34:48
Message-ID: 8805f7e2d8cff82279a19e33afa9435d () localhost ! localdomain
[Download RAW message or body]

> The purpose of the token is to permit different sources of randomness.
Seeing as how you don't allow anything other than
`nacl_secure_random_init`, perhaps you should just make the default token
be the empty string in the `<random>` header.

That would be a breaking change if we do decide to support other sources of
randomness. What we have now emulates the token it accepts (its POSIX
meaning), so it's the right thing IMO.

http://reviews.llvm.org/D6442



_______________________________________________
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
[prev in list] [next in list] [prev in thread] [next in thread]