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,f93e461e8491e322 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon02.news.prodigy.net!prodigy.net!newsfeed-00.mathworks.com!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Limited_Controlled, orthogonality and related issues Date: Fri, 19 Jan 2007 10:29:35 -0500 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls6.std.com 1169220576 20739 192.74.137.71 (19 Jan 2007 15:29:36 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Fri, 19 Jan 2007 15:29:36 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:d2g2pDPTMunC3KZUgwOr+E6Un+Q= Xref: g2news2.google.com comp.lang.ada:8330 Date: 2007-01-19T10:29:35-05:00 List-Id: Maciej Sobczak writes: > So, my simple decision to make T and S controlled required: > > 1. Changing the signatures of Do_The_Job and gazillion of similar > subprograms. > 2. Adding the tagged keyword in the public view for T and S. > > In conclusion, my decision to make T and S controlled appeared to not be > orthogonal to the rest of the package. I really can't get too excited about the fact that a change to the package required other changes to the same package. If you said that clients had to change, that would be a much bigger problem. Possible solutions: Allow 'Class on untagged types. Use special syntax to distinguish dispatching operations. Make all types tagged. For efficiency, this would require a different run-time model than what Ada compilers currently do -- you don't want to store a tag field with every Boolean variable! To enable the non-stored-tag model, eliminate the rule that all tagged parameter are aliased (and allow "aliased" keyword). None of the above are likely to happen, I suspect. - Bob