Dirk Eddelbuettel wrote:

<snip>

Or do you claim that not-using
   gsl_rng_alloc (gsl_rng_default)

leading to a SEGV is a invalid behaviour?  I am much less convinced that that
is a valid bug report -- it's much like using un-alloc'ed pointer types in
my book.

That is my claim, yes; I'd content that a very simple sanity-check-and-error message would be better behaviour from a library in this case. I conceed that it's arguable, but IMAO gsl should emit an error rather than SEGV on bad input to any of its functions, unless it's unreasonably expensive to do the error-checking.

Regards,

Matthew

--
Matthew Vernon, Research Fellow
Ecology and Epidemiology Group,
University of Warwick
http://blogs.warwick.ac.uk/mcvernon



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to