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,d8aa0b11d3c79b63 X-Google-Attributes: gid103376,public From: Robert A Duff Subject: Re: Access to strings and string subtypes? Date: 2000/03/17 Message-ID: #1/1 X-Deja-AN: 598794921 Sender: bobduff@world.std.com (Robert A Duff) References: <38d10a7b.91796987@news.rrds.co.uk> <38d11f2a.97092271@news.rrds.co.uk> <2000Mar17.070235.1@eisner> <8atgul$i7l$1@nnrp1.deja.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 2000-03-17T00:00:00+00:00 List-Id: Robert Dewar writes: > No one has answered the original question of WHY this annoying > limitation is in Ada95. It is a (misguided in my opinion) > worry about efficiency. It allows implementations to omit > templates on objects with explicit bounds to save a little > bit of space. I don't think it was purely an efficiency issue. I think we were concerned that existing Ada 83 implementations were already doing that optimization, and would have difficulty changing the way they represent arrays. So we might have decided differently if we were designing a new language from scratch -- I'm not sure. I agree that the restriction is somewhat annoying. I also don't like rules that make arrays and discriminated types gratuitously different -- in my opinion, bounds and discriminants are (or at least *should* be) essentially the same thing. - Bob