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: 109fba,f92fbb4a0420dd57 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,f92fbb4a0420dd57 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: some questions re. Ada/GNAT from a C++/GCC user Date: 1996/04/03 Message-ID: #1/1 X-Deja-AN: 145728334 references: <315D902C.6F7B@escmail.orl.mmc.com> <4jmuj5$lkh@dayuc.dayton.saic.com> <315F4A9D.7E6F@mcs.com> <4jq4vd$2s5@ferrari.NetXpress.com> <4jsesm$gpa@fozzie.sun3.iaf.nl> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada,comp.lang.c++ Date: 1996-04-03T00:00:00+00:00 List-Id: Geert said "You still forgot to mention something: Also for humans (at least for this human) it is simply easier to parse source code that has all of the declarations in one section. " Absolutely, that hits it on the head! We often design in restrictions for purely methodological reasons, even though they do not help the compiler, and may actually complicate the compiler. For example, in Ada, we do not permit a goto to leave a procedure body. Allowing this is perfectly easy, but it creates a program structure that we prefer to to permit.