From: Brian Gough <bjg@network-theory.co.uk>
To: "Robert G. Brown" <rgb@phy.duke.edu>
Cc: GSL Discussion list <gsl-discuss@sources.redhat.com>
Subject: Re: RNG question
Date: Mon, 11 Aug 2008 20:47:00 -0000 [thread overview]
Message-ID: <87bpzzi8k8.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0808080823080.1860@lilith.rgb.private.net>
At Fri, 8 Aug 2008 08:28:07 -0400 (EDT),
Robert G. Brown wrote:
> Are future/new rngs going to always be added at the end (new numbers) or
> will they get inserted in typed groupings?
They could go anywhere, the order is not guaranteed to be preserved.
--
Brian Gough
next prev parent reply other threads:[~2008-08-11 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 23:32 Robert G. Brown
2008-08-05 9:05 ` Fabian Bastin
2008-08-08 11:12 ` Brian Gough
2008-08-08 12:33 ` Robert G. Brown
2008-08-11 20:47 ` Brian Gough [this message]
2008-08-18 21:12 ` Robert G. Brown
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 10:25 rng question Jari Häkkinen
2005-12-07 20:07 ` Brian Gough
2005-12-09 13:49 ` Jari Häkkinen
2005-12-17 16:50 ` Brian Gough
2005-12-17 23:58 ` Jari Häkkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bpzzi8k8.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=rgb@phy.duke.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).