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,e507e3d80b7abf1e X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Fun with WebAda/GNAT Date: 1996/08/22 Message-ID: #1/1 X-Deja-AN: 175849272 references: <32120233.484C@lmtas.lmco.com> <4uv6bs$ffd@dfw.dfw.net> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-08-22T00:00:00+00:00 List-Id: Ronald Cole says "> We have discussed this, but path names in typical Unix systems are so > long that this generates an unacceptable level of noise in the normal > case. If you're willing to toss out clarity and exactness in favor of aesthetic pleasantness, then so be it. It's your compiler and your error messages..." On the contrary, it does NOT improve clarity at all to give full path names, but instead obscures the clarity of the messages in the normal case. Given that you can trivially find out what file is being referenced in the rare case where you don't immediately know, it seems clear that it is best NOT to disturb the clarity of ordinary messages. If you want to experiment with this, it is an obvious one token chanbge in errout to generate the full file name ...