From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,14be6619f79b4573 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news2.google.com!proxad.net!usenet-fr.net!news.enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Duncan Sands Newsgroups: comp.lang.ada Subject: Re: Hashing on System.Address Date: Tue, 14 Jun 2005 11:09:56 +0200 Organization: Cuivre, Argent, Or Message-ID: References: <42AE9AD6.80803@mailinator.com> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: melchior.cuivre.fr.eu.org 1118740226 38406 212.85.156.195 (14 Jun 2005 09:10:26 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Tue, 14 Jun 2005 09:10:26 +0000 (UTC) Cc: "Alex R. Mosteo" To: comp.lang.ada@ada-france.org Return-Path: User-Agent: KMail/1.8.1 In-Reply-To: <42AE9AD6.80803@mailinator.com> Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: g2news1.google.com comp.lang.ada:11342 Date: 2005-06-14T11:09:56+02:00 > > By the way, is there any reason why Ada.Containers doesn't provide some > > standard hash functions? I reckon hashing on strings and on addresses > > would be pretty handy. > > Out of Containers hierarchy: Ada.Strings.Hash You know, this implementation advice sounds pretty silly: Implementation Advice 7/2 The various Hash functions should be good hash functions, returning a wide spread of values for different string values. It should be unlikely for similar strings to return the same value. As if any implementor needs to be told that they should use a "good" rather than a "bad" hash function! Ciao, d.