Access 'out' parameter as attribute prefix AI-00840/00 1 89-11-19 ST RE !standard 04.01 (04) 89-11-19 AI-00840/00 !class study 89-11-19 !status received 89-11-19 !topic Access 'out' parameter as attribute prefix !summary 89-11-19 !question 89-11-19 !recommendation 89-11-19 !discussion 89-11-19 !appendix 89-24-08 ***************************************************************************** !section 04.01 (04) Hans Hurvig 89-24-08 83-01328 !version 1983 !topic Access 'out' parameter as attribute prefix !reference 6.2(5), A62006D.ADA, B62006C.ADA The rule in 4.1(4) forbidding an access 'out' parameter as a prefix for any attribute is overly restrictive. Its justification is that such an appearance can imply that the access value is dereferenced in connection with appropriateness: 'CALLABLE, 'FIRST, 'LAST, 'LENGTH, 'RANGE, and 'TERMINATED. But using an access 'out' parameter as a prefix for other attributes is harmless, and making it illegal is a distinct loss of functionality. For instance, 'ADDRESS is quite well-behaved for any 'out' parameter, and it is very odd indeed to single out those that happen to have an access type. I'd argue that the rule in 4.1(4) should simply be deleted as redundant; paragraph 6.2(5) says that an 'out' parameter cannot be read, and using an access object as a prefix for an appropriate-attribute constitutes reading, because it refers to the denoted entity, thereby making it illegal.