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,91c7c63c23ef2d0c X-Google-Attributes: gid103376,public From: Dale Stanbrough Subject: Re: Beware: Rep spec on an enumeration type ... Date: 1997/12/19 Message-ID: <67cqsh$q8t$1@goanna.cs.rmit.edu.au>#1/1 X-Deja-AN: 308503487 Distribution: world Content-Transfer-Encoding: 8bit References: Content-Type: text/plain; charset=ISO-8859-1 X-XXMessage-ID: Organization: RMIT Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1997-12-19T00:00:00+00:00 List-Id: Robert Dewar writes: "You ask above for a "focused effort .. solving the problems ...", but you have in mind that the solution is to build an FAQ which will provide simplistic rules (e.g. "never use formatted IO") that will magically solve your problems. Sorry, I don't think this is feasible!" ...but an FAQ that says "most of Ada is pretty predicatable, and like most other languages (e.g. loops, if statements), but watch out for these bits, they can be tricky and have unforseen consequences" would be useful." (i'm writing one right now, actually :-) Besides such lists allow people to understand better what Ada is about, depending on the coverage (e.g. it could also cover things such as "a package is not a type", as one review a year or two back managed to get wrong (still!)). Dale