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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!hplabs!hpda!hpcuhb!hpcllla!hpclisp!defaria@hpclapd.HP.COM
From: defaria@hpclapd.HP.COM (Andy DeFaria)
Newsgroups: comp.lang.ada
Subject: Re: File name conventions for Ada units
Message-ID: <920036@hpclapd.HP.COM>
Date: 12 Oct 90 05:29:41 GMT
References: <589@censun1.UUCP>
Organization: Hewlett-Packard Calif. Language Lab
List-Id: <comp.lang.ada>

>/ hpclapd:comp.lang.ada / brnstnd@kramden.acf.nyu.edu (Dan Bernstein) /  1:59 am  Oct 11, 1990 /
>
>The beauty of this system being that if sourcefile is ever removed
>accidentally, you end up using sourcefile.ada even if it is entirely
>different. This contributes greatly to bug concealment, unreliability,
>and other software engineering techniques.

The    person  that   names one   file    sourcefile  and  a  different one
sourcefile.ada deserves what he gets!   

Same kind of problems occur with things like linked  files  and unprintable
characters in  file  names.  A certain amount of  knowledge about  the file
system and its behaviour has to be assumed.