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=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.182.118.194 with SMTP id ko2mr2387622obb.32.1395979846883; Thu, 27 Mar 2014 21:10:46 -0700 (PDT) Path: border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!l13no12016594iga.0!news-out.google.com!xg2ni63igc.0!nntp.google.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!fx10.iad.POSTED!not-for-mail From: Shark8 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:31.0) Gecko/20100101 Thunderbird/31.0a1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Augusta: An open source Ada 2012 compiler (someday?) References: <1f0a85a6-ea4d-4d30-8537-0ce9063f992a@googlegroups.com> <89a0ea84-83e2-4693-b2ea-ea9da65bbc73@googlegroups.com> <1793575416417652043.069687laguest-archeia.com@nntp.aioe.org> In-Reply-To: <1793575416417652043.069687laguest-archeia.com@nntp.aioe.org> Message-ID: X-Complaints-To: abuse@teranews.com NNTP-Posting-Date: Fri, 28 Mar 2014 04:10:46 UTC Organization: TeraNews.com Date: Thu, 27 Mar 2014 22:12:47 -0700 X-Received-Bytes: 2489 X-Received-Body-CRC: 2216776962 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Original-Bytes: 2866 Xref: number.nntp.dca.giganews.com comp.lang.ada:185387 Date: 2014-03-27T22:12:47-07:00 List-Id: On 27-Mar-14 15:32, Luke A. Guest wrote: > Niklas Holsti wrote: >> On 14-03-27 21:38 , Lucretia wrote: >>> I've already mentioned doing this on #Ada, a fork of Ada. >>> Take the basic language, strip it down to the basics >> >> So, what are the "basics"? > > The basics are the main language. > >> version of Ada-Ed, but with acceptable performance for programs that are >> not humongously large. At the same time, such work, at least if done in >> an academic setting, could help to clarify the dark corners of the >> language standard. > > Can be done with llvm as a start with the hit interface. > >>> 3) Replace tagged with just class, so: >>> >>> type C is >>> class >>> ... >>> end class; >> >> A mere sop to foreign conventions and creates useless non-uniformity >> between different kinds of records. I'm against it. > > Sop?? > > The class is a different concept to a record and should be implemented that > way, this will also make it more familiar to others, I.e. Help foster > adoption. I'd rather CLASS be used as, say, a shorthand for [essentially] signature-package use-cases (i.e. ensuring some type has some interface -- perhaps allowing a separately defined implementation).