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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Interesting article on ARG work Date: Mon, 9 Apr 2018 21:47:59 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <1b44444f-c1b3-414e-84fb-8798961487c3@googlegroups.com> <62ee0aac-49da-4925-b9aa-a16695b3fc45@googlegroups.com> <9879872e-c18a-4667-afe5-41ce0f54559f@googlegroups.com> <80db2d05-744f-4201-ba1b-4436f8040491@googlegroups.com> <59f9ab6d-d6ba-45ff-a6f0-c5699983d9e8@googlegroups.com> <1a390e22-f49f-4028-8e58-ca4d0f51e4b6@googlegroups.com> NNTP-Posting-Host: kQkuQcRDy1QFvWpyB1foYw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.3 Xref: reader02.eternal-september.org comp.lang.ada:51421 Date: 2018-04-09T21:47:59+02:00 List-Id: On 2018-04-09 18:45, Niklas Holsti wrote: > You seem to be suggesting a specific way to use "@" to include/exclude > entire statements (not text lines) from the effective code. Right: - statements in the context of control flow; - declarations in the context of declarations; - Boolean expression within an expression (replaced by False when removed). Conditional declaration are invisible outside conditional code: declare @ X : Integer; begin X := 1; -- Illegal, X is not visible Unconditionally declared objects are immutable within conditional code. declare X : Integer; begin @ X := 1; -- Illegal, X is read-only Maybe this rule should be relaxed a bit. > Could you > please make your suggestion explicit? For example, with regard to the > need (or perhaps not) to have at least a "null;" statement in each branch. All rules regarding null, return apply: if Foo then @ null; -- Illegal, statement is expected end if; function Foo return Integer is begin null; @ return 123; end Foo; -- Illegal, no return statement But this is legal: function Foo return Integer is begin @ return 123; return 122; end Foo; BTW, I don't like @ much. Maybe there should be a better syntax, especially to support multiple conditional spaces, e.g. for different things to debug. A sort of brackets would work better: pragma Debug (Pool) do -- Debugging code for Poll end Debug; -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de