From maine@altair.dfrc.nasa.gov Mon Dec 22 21:03:24 1997 Received: from altair.dfrc.nasa.gov (altair.dfrc.nasa.gov [130.134.65.117]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id VAA16048 for ; Mon, 22 Dec 1997 21:03:23 +0100 Received: (from maine@localhost) by altair.dfrc.nasa.gov (8.8.6/8.8.6) id MAA07573; Mon, 22 Dec 1997 12:03:21 -0800 (PST) Date: Mon, 22 Dec 1997 12:03:21 -0800 (PST) Message-Id: <199712222003.MAA07573@altair.dfrc.nasa.gov> From: Richard Maine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: sc22wg5@dkuug.dk Subject: Re: (SC22WG5.1477) Edit missing from N1282 (allocatable TR) In-Reply-To: <349EC252.796D@mixcom.com> References: <199712221848.TAA15179@dkuug.dk> <349EC252.796D@mixcom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Craig T. Dedo writes: > This is a very serious technical error. Leaving this mistake in the TR > will directly contradict the clear intent and purpose of the TR, with > consequent complications for implementors. Well, that seems to me like a bit of an overstatement. Specifically because the intent of the TR in the matter is clear and explicit, it makes it pretty obvious that this was just an unintentional omission. The TRs are, after all, half experimental and thus don't have quite the formal weight of a full-blown standard. Since the intent is so obvious in this particular matter, I have trouble imagining it really causing any implementors difficulty. Sure, they are likely to notice the discrepancy and point it out, possibly even in the form of a question. But can you actually believe that any implementor would note that there was no edit to that constraint and conclude, therefore, that 2/3 of the TR was moot because it describes as an academic excercise how those 2 features (allocatable dummies and function results) would work if we allowed them, but we don't actually allow them? I can't. On the other hand, I certainly agree that it would be better to fix the TR. I just don't see it as a critical "by whatever means necessary" issue. -- Richard Maine maine@altair.dfrc.nasa.gov