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.0 required=5.0 tests=BAYES_20,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b5ab7c96b188b59e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-13 09:55:14 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed00.sul.t-online.de!t-online.de!peernews3.colt.net!newsfeed.stueberl.de!teaser.fr!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: "amado.alves" Newsgroups: comp.lang.ada Subject: RE: The "()" operator revisited. Date: Tue, 13 Jan 2004 17:53:24 -0000 Organization: Cuivre, Argent, Or Message-ID: NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: melchior.cuivre.fr.eu.org 1074016413 58582 80.67.180.195 (13 Jan 2004 17:53:33 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Tue, 13 Jan 2004 17:53:33 +0000 (UTC) To: "Hyman Rosen" , Return-Path: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Thread-Topic: The "()" operator revisited. Thread-Index: AcPZ+joU3+m5/exkS06y9/P64TDedwAA0Aw5 X-OriginalArrivalTime: 13 Jan 2004 17:53:25.0637 (UTC) FILETIME=[24A74B50:01C3D9FE] 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.3 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:4373 Date: 2004-01-13T17:53:24+00:00 "You should begin to see why C++ templates don't come with a mechanism to specify restrictions on parameters, and instead rely on seeing if usage within the code is legal." Right, and on Future_Language we will have the best of both worlds: any = degree of restriction on the parameter definition. Currently I simulate = classes outside the established set with formal packages.