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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5fc9b3bec63cb80b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-13 16:05:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.stueberl.de!newspeer1-gui.server.ntli.net!ntli.net!news8-gui.server.ntli.net.POSTED!53ab2750!not-for-mail From: "chris.danx" Newsgroups: comp.lang.ada References: Subject: Re: Any type, any type at all! X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 x-mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: Date: Sun, 14 Jul 2002 00:04:07 +0100 NNTP-Posting-Host: 80.5.140.234 X-Complaints-To: abuse@ntlworld.com X-Trace: news8-gui.server.ntli.net 1026601498 80.5.140.234 (Sun, 14 Jul 2002 00:04:58 BST) NNTP-Posting-Date: Sun, 14 Jul 2002 00:04:58 BST Organization: ntl Cablemodem News Service Xref: archiver1.google.com comp.lang.ada:27074 Date: 2002-07-14T00:04:07+01:00 List-Id: > I've been reading through the proposed DOM Level 3 spec and was wondering > how an implementation could handle some of the new requirements for core > compliance. In particular the DOMUserData type (section 1.1.7) > > To quote: > > > Type Definition > > > > A DOMUserData represents a reference to an application object. > > It can't be generic can it? That would mean you couldn't mix types within > the DOM, which is from my interpretation, the intention of this type. > > I can think of one way involving (access to) classes, which makes it a tad > ugly for simple types like Integers, Strings, etc, but to me it seems the > only way. Any thoughts on how to handle this in Ada (from someone more > experienced)? No comments?