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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f92fbb4a0420dd57 X-Google-Attributes: gid103376,public From: mab@dst17.wdl.loral.com (Mark A Biggar) Subject: Re: some questions re. Ada/GNAT from a C++/GCC user Date: 1996/04/03 Message-ID: <4ju9o2$3de@wdl1.wdl.loral.com>#1/1 X-Deja-AN: 145631350 references: organization: Loral Western Development Labs newsgroups: comp.lang.ada Date: 1996-04-03T00:00:00+00:00 List-Id: In article bcf@ssd.ray.com (Felaco) writes: >Anyway, it would have been *nice* if we could dispense with the 'declare' >and the 'end' when a new scope is introduced anyway, like in an if block >or a loop. I don't see how backwards compatibility with Ada83 would be >compromised, or any other rules would have to change. >ie: > if whatever then > X : Integer; > Y : Some_Task_Type; > begin > do_something; > else > loop > Y : Boolean; > begin > do_something_else; > exit when Y; > end loop; > end if; >I find the above just as human-readable, and still machine-readable. The >presence of the declaration signals that a new scope is introduced, the >begin serves as a separator and the else serves as the end. Why not? Hum, that may be machine readable, but its not easily machine readable. It appears to require arbitrarily long look ahead to parse (mainly because of pragmas). -- Mark Biggar mab@wdl.loral.com