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,a92e43963a6b930f X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!newsfeed2.dallas1.level3.net!news.level3.com!bloom-beacon.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: N best things about Ada? Date: Mon, 12 Jul 2010 11:13:44 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <97691fd2-7411-4ccc-bc7b-290aca633cd5@z30g2000prg.googlegroups.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls4.std.com 1278947608 15871 192.74.137.71 (12 Jul 2010 15:13:28 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Mon, 12 Jul 2010 15:13:28 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:oO5K+5yhlDqfAVloodFanUHd2tw= Xref: g2news1.google.com comp.lang.ada:12342 Date: 2010-07-12T11:13:44-04:00 List-Id: Shark8 writes: > People have mentioned packages, non-textual-substitution generics, and > such. > But one thing that could come in handy is the named parameters, and it > is something I like; one of those "little things." Yes. It's such a small feature, yet has a huge benefit. People should use it more often. Another small feature: underscores in numeric literals. One of my pet peeves is when I have to carefully count the zeroes in 10000000, when it's so easy to write 10_000_000. > "Circle( Radius => 23, X => 28, Y => 14 );" will always be more > readable than "Circle( 23, 28, 14 );" plus, there's the added benefit > that 1) changes in parameter-ordering will not impact calls of this > sort, & 2) the users of the functions/procedures can place the more > pertinent parameters [to their task] more prominently [e.g. first]. Do you have any examples of that last part? That is, examples where using different parameter orders in different calls makes the code more readable? I think that sort of inconsistency usually makes the code less readable. I wouldn't mind a rule that says the parameter order has to match the declaration. (A Legality Rule, not a Name Resolution Rule!) - Bob