Re: Most important QC of the year

From: Jolyon Smith <jolyons@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 18 Jul 2006 10:34:12 +1200

In article <44bc03f9$1@xxxxxxxxxxxxxxxxxxxxxx>, "somebody" <A> says...

But the distribution will be far from uniform in a typical application, more
like an exponential with many of the strings being compared couple of (or
exactly 1) characters long.

Indeed, I wasn't being _entirely_ serious, just an abiding idle
amusement with the distinction between "Odds"/"Probability" and
"likelihood".

;)

--
Jolyon Smith
.

References:
- Re: Most important QC of the year
  - From: Jolyon Smith

Prev by Date: Re: Borland set to sell IDE business
Next by Date: Re: Best way of Parsing SQL statement for Parameters....
Previous by thread: Re: Most important QC of the year
Next by thread: where to find attachment of an old post
Index(es):
- Date
- Thread

Relevant Pages

Re: Why R6RS is controversial
... the semantics of the language, ... behavior of grapheme-cluster characters under most linguistic ... as the strings grow longer. ... Normalization is hideously complicated, and may require many ...
(comp.lang.scheme)
Re: Unicode LISP??
... I'm not experienced with Common Lisp library, ... terms of strings rather than characters. ... have their representation upgraded if they are updated in place. ...
(comp.lang.lisp)
Re: not quite 1252
... The kill_gremlins function is intended to fix Unicode strings that have been obtained by decoding 8-bit strings using 'latin1' instead of 'cp1252'. ... In fact it wasn't, it was UTF-8 like Sergei wrote, but it was easy to convert it to cp1252, no problem. ... characters to documents marked up as ISO 8859-1 or other encodings. ...
(comp.lang.python)
Re: How to check variables for uniqueness ?
... FI in English typography), so the correct uppercase version of those ... characters is the sequence SS. ... So you at least agree with me that it should be consistent with toUpperCase -- all strings should have a single canonical toUpperCase, a single canonical toLowerCase, both should define equivalence classes on the mixed-case input strings, these should be the SAME equivalence class, and equalsIgnoreCase should implement and embody the corresponding equivalence relation. ... The version that doesn't shouldn't surprise English speakers; the version that does shouldn't surprise anyone familiar with its locale-specific behavior for the locale actually used. ...
(comp.lang.java.programmer)
Re: How to check variables for uniqueness ?
... characters is the sequence SS. ... is simply capitalizing strings. ... The fact that case mapping in English /is/ simple is neither here not ... That is a fair criticism of the Unicode position. ...
(comp.lang.java.programmer)