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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,103b407e8b68350b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-07 19:42:14 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!news-out.cwix.com!newsfeed.cwix.com!nntp.abs.net!uunet!dca.uu.net!ash.uu.net!spool0900.news.uu.net!reader0902.news.uu.net!not-for-mail Date: Tue, 07 Jan 2003 22:41:48 -0500 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Anybody in US using ADA ? One silly idea.. References: <1041908422.928308@master.nyc.kbcfp.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1041997309.165001@master.nyc.kbcfp.com> Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1041997310 reader2.ash.ops.us.uu.net 17897 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:32720 Date: 2003-01-07T22:41:48-05:00 List-Id: Dmitry A. Kazakov wrote: > This is also possible with tagged types. You are free to make > operations inline. The compiler may remove the type tag if it is > statically known. Under these conditions a static dispatch would cost > nothing. The point here is using your newly created types with libraries of existing code which are to operate on those types. If those libraries are generic, then it may be possible to get significant inlining benefits. If those libraries operate on tagged types, then it won't matter that *you* know the static type in your code, because the library won't. It's the difference, in C++ terms, between qsort and std::sort. The former takes a pointer to function which it must call for each comparison, while the latter can inline the comparison.