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,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e1bb9627c57b7d5b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-15 17:25:54 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.vmunix.org!news.cs.univ-paris8.fr!teaser.fr!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: "Alexandre E. Kopilovitch" Newsgroups: comp.lang.ada Subject: Re: U : Unbounded_String := "bla bla bla"; (was: Is the Writing...) Date: Thu, 16 Oct 2003 04:31:26 +0400 (MSD) Organization: Cuivre, Argent, Or Message-ID: References: NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1066263890 23545 80.67.180.195 (16 Oct 2003 00:24:50 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Thu, 16 Oct 2003 00:24:50 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: In-Reply-To: ; from "(see below)" at Wed, 15 Oct 2003 20:38:24 GMT X-Mailer: Mail/@ [v2.44 MSDOS] X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Gateway to the comp.lang.ada Usenet newsgroup List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:928 Date: 2003-10-16T04:31:26+04:00 "(see below)" wrote: > > type Flex is private; > > for Flex'Literal_Conversion use To_Flex; > ... > > My concern is quite opposite: I'd like have a control for blocking such > > overloadings (thus denying an opportunity for multiple literal types for a > > given type), > > for Flex'Literal_Conversion use <>; -- ?? Well, I don't see this form as informative, but I must confess that here I'm guilty myself, because this part of my concern was probably a sort of self-inflicted FUD. But > > including those that may emerge within a derivation of a new type; > > for Flex'Class'Literal_Conversion use <>; -- ?? this part of the concern is real, and idea about 'Class seems interesting and perhaps good enough. I think that the angle brackets are actually not needed here, we can simply write: for Flex'Class'Literal_Conversion use To_Flex; and this will mean that for all types belonging to Flex'Class two restrictions are in effect: 1) To_Flex functions declared in other packages cannot be used for conversions of literals; 2) Literal_Conversion attribute cannot be (re)defined in other packages. So, there will be a clear difference between for Flex'Literal_Conversion use To_Flex; and for Flex'Class'Literal_Conversion use To_Flex; Alexander Kopilovitch aek@vib.usr.pu.ru Saint-Petersburg Russia