NICE-ESG-Libs Digest        Tue, 12 Sep 95       Volume 1 : Issue 289 

Today's Topics:
                             valid_index


NICE Eiffel Standards Group -- Library Committee Mailing List To post to list: NICE-ESG-Libs@atlanta.twr.com To send mail to the Chairman of the committee: NICE-ESG-Libs-chair@atlanta.twr.com Administrative matters (sign up, unsubscribe, mail problems, etc): NICE-ESG-Libs-request@atlanta.twr.com
Date: Tue, 12 Sep 95 15:45:13 PDT From: bertrand@eiffel.com (Bertrand Meyer) Subject: valid_index To: nice.lib@eiffel.com Copy to: From: Bertrand Meyer Mailer: BOOM Dear Colleagues: Just a point of cosmetics. I saw somewhere a proposal to include a function `valid_index' to ARRAY. I haven't really formed an opinion, but if such a function or its equivalents elsewhere were to be adopted I think we should use names such as `correct_index'. ETL is quite strict in using the word ``valid'' to denote adherence to static semantic rules (``validity constraints''), as opposed to ``correct'' which applies to dynamic semantics (e.g. adherence to assertions). The distinction is important - although the choice of words is admittedly arbitrary - so we should try to keep it in the libraries. ISE's EiffelBase does use terms like `valid_key' (in HASH_TABLE) but that's not a reason to put such names into ELKS. (But no doubt someone will find a dark commercial reason behind my suggestion - after all I am a ``vendor''.) Best regards, -- BM