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,FREEMAIL_FROM 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: Victor Porton Newsgroups: comp.lang.ada Subject: When to use formal discrete type? Date: Wed, 29 Nov 2017 21:04:32 +0200 Organization: Aioe.org NNTP Server Message-ID: NNTP-Posting-Host: ixW2q+EPQygHpaL7GaA/ag.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.14.10 X-Notice: Filtered by postfilter v. 0.8.2 Xref: reader02.eternal-september.org comp.lang.ada:49255 Date: 2017-11-29T21:04:32+02:00 List-Id: I am creating a generic package which accepts as a formal argument a type which is expected to be an enumeration type. Should for this enumeration argument I use formal private type (is private) or formal discrete type (is (<>))? I do not use features specific to discrete types such as 'First or 'Range attributes. Because it easily generalizes from discrete types to arbitrary private types, should I do generalization? What of (generalizing for all private types or not) the two is better: a. for clarity of code; b. for performance? It there a noticeable difference in performance if I generalize? -- Victor Porton - http://portonvictor.org