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,e3c7ee8cd1d3f414 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: rep clause in generics Date: 1997/03/15 Message-ID: #1/1 X-Deja-AN: 225803206 References: <01bc3057$61a78db0$81946482@vkpc131> <3329512E.4900@gsfc.nasa.gov> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-03-15T00:00:00+00:00 List-Id: iJonas said <> That's not the correct way to reason. Whether an expression is static or not is NOT a question of whether the value is determined at run time or not. There are lots of examples of values that are known at compile time but are not static expressions. The rules on static expressions are in RM 4.9. An expression is static iff the rules in 4.9 say it is static. period. Now in this case, there is no rule that says this expression is static, but the reasoning is confusing (for example, by this reasoning, one would expect that 'Size applied to a digits formal should be static, because certainly the size is known at compile time, since it is fixed for any particular instantiation). But this reasoning is faulty, as 4.9 shows, since x'size is still non-static for a formal digits type x, since there is no rule that says it is static.