Re: Lists of size Integer.MAX_VALUE

Lew wrote:
[...]
The point here, as with the bug in quicksort that went undetected for about forty years [1], is that even the designers missed the corner cases.

[1] <http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html>

An interesting reference, but one which does not contain
the word "quicksort" nor even "quick" ...

--
Eric Sosman
esosman@xxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: Lists of size Integer.MAX_VALUE
    ... Eric Sosman wrote: ... The point here, as with the bug in quicksort that went undetected for about forty years, is that even the designers missed the corner cases. ...
    (comp.lang.java.programmer)
  • Re: eval(000052) = 42?
    ... Is this a known bug in the eval function? ... Forty plus two is forty two. ... So is this anachronism slated for removal in Python 3? ...
    (comp.lang.python)
  • Re: selecting random array elements
    ... Lew wrote: ... Just for posterity's sake, I found a bug in my code after I posted. ... Code re-use is always preferred. ...
    (comp.lang.java.help)
  • Re: eval(000052) = 42?
    ... Is this a known bug in the eval function? ... Forty plus two is forty two. ... hasn't anyone told you not to play with the eval function? ... You could catch something nasty. ...
    (comp.lang.python)
  • Re: interesting task for .NET learners: why ArrayList.Sort hangs? [.NET 1.1]
    ... a bug in the quicksort in 1.1? ... Prev by Date: ...
    (microsoft.public.dotnet.languages.csharp)