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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,7502ddf2c6c41330 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail From: "Martin Dowie" Newsgroups: comp.lang.ada Subject: Re: Missing features in Ada.Containers Date: Fri, 8 Oct 2004 11:07:34 +0100 Organization: BAE SYSTEMS Message-ID: <41666578$1_1@baen1673807.greenlnk.net> References: <416657E2.9050503@mailinator.com> X-Trace: news.uni-berlin.de Jgr5WznBcXtx1pVNZKxnmguzJei9xeHogDVqHcBDHZAK6XEPud X-Orig-Path: baen1673807.greenlnk.net!baen1673807!not-for-mail X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Original-NNTP-Posting-Host: baen1673807.greenlnk.net Xref: g2news1.google.com comp.lang.ada:4919 Date: 2004-10-08T11:07:34+01:00 List-Id: Alex R. Mosteo wrote: > Of the top of my head I find notable the absence of the "hashed > strings" container. Now it seems you're alone with a "hashed map" > whose keys are generic of constrained nature. Thus you must make some > leaps to have the old (and in my case, most used) hashed string > container. Indeed it requires ugly conversions between the key type, > String, defining the hashing function simply to reuse the > Ada.Hash_String, etc. It smells so wrong to me that I'm almost sure > I'm missing something obvious here. Can't you use "Ada.Containers.Indefinite_Hashed_Maps"?