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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Path: border2.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!border2.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.glorb.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!fx26.iad.POSTED!not-for-mail From: Shark8 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:32.0) Gecko/20100101 Thunderbird/32.0a1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada platforms and pricing, was: Re: a new language, designed for safety ! References: <255b51cd-b23f-4413-805a-9fea3c70d8b2@googlegroups.com> <5ebe316d-cd84-40fb-a983-9f953f205fef@googlegroups.com> <2100734262424129975.133931laguest-archeia.com@nntp.aioe.org> <5156oy7vhg99.17wu6q2ef45ke.dlg@40tude.net> <18et97c0c22vc$.y98lxxfblijn.dlg@40tude.net> <08f83f70-ccb1-45ec-8a4c-46e3442745b8@googlegroups.com> <557db566-fa02-4978-8798-50a097aa5407@googlegroups.com> In-Reply-To: <557db566-fa02-4978-8798-50a097aa5407@googlegroups.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Message-ID: X-Complaints-To: abuse@teranews.com NNTP-Posting-Date: Tue, 24 Jun 2014 15:55:17 UTC Organization: TeraNews.com Date: Tue, 24 Jun 2014 09:55:15 -0600 X-Received-Bytes: 2427 X-Received-Body-CRC: 299967629 X-Original-Bytes: 2730 Xref: number.nntp.dca.giganews.com comp.lang.ada:187223 Date: 2014-06-24T09:55:15-06:00 List-Id: On 24-Jun-14 05:25, Dan'l Miller wrote: > No, Shark8, that is the epitome of *not* direct representation of state-machines > as a first-class citizen in {Ada, C, C++, ...}, because the compiler has > absolutely no clue that all the enumerations & branching are representing an FSM. I said direct representation, not first-class citizen -- or are you saying that both must be present? Also, why should the compiler 'need' to be aware of what's going on? It's already got the rules that ensure correctness: no state/event can be omitted. (Ensuring that all transitions are correct-implementation are of the same class as misprinted specs where 'and' was used instead or 'or'.) Something where state-machines are first-class citizens seems like an appropriate use for a DSL.