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,9768c08202fdbbb1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-10 21:48:43 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!diablo.theplanet.net!zen.net.uk!news.cabal.org.uk!news-peer.gradwell.net!not-for-mail Newsgroups: comp.lang.ada From: porton@ex-code.com (Victor Porton) Date: Mon, 11 Nov 2002 10:28:19 +0500 References: <3dcb8347$0$299$bed64819@news.gradwell.net> Organization: Extreme Code Software (http://ex-code.com) Subject: Re: Let's change semantics of "use type" Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Content-Type: text/plain; charset=us-ascii X-URL: http://www.ex-code.com/ Message-ID: <3dcf44bb$0$300$bed64819@news.gradwell.net> NNTP-Posting-Date: 11 Nov 2002 05:48:43 GMT NNTP-Posting-Host: 195.149.39.13 X-Trace: 1036993723 news.gradwell.net 300 mail2news/195.149.39.13 X-Complaints-To: news-abuse@gradwell.net Xref: archiver1.google.com comp.lang.ada:30702 Date: 2002-11-11T05:48:43+00:00 List-Id: In article , Robert A Duff writes: > porton@ex-code.com (Victor Porton) writes: > >> In article , >> Robert A Duff writes: >> > porton@ex-code.com (Victor Porton) writes: >> > >> >> I am suggesting (for the next Standard) to change the semantics of "use >> >> type" so that it would make visible not only primitive _operators_, but >> >> all primitive _operations_. > > My point was that changing the syntax from "use P;" to "use all P.T;" > won't eliminate the supposed "dangers" of use clauses. Most packages > contain a type, plus operations on the type, so the two syntaxes mean > *almost* the same thing, in practice. "use all type" is namely against such the packages which contain something other among operations on a type and also against such packages which define several types. Consider also packages which define operations on class wide types. "use"ing such a package may be dangerous as it may bring operations on a not supposed concrete types. Well, which dangers "use all type" has? Personally I when deal with a type almost always want all its primitive operations. Getting all primitive operations of a type seems nearly safe. Also both standartizing and implementing "use all type" would be *very* simple. Why not?