Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!ames!ucbcad!ucbvax!jade!eris!mwm From: mwm@eris.BERKELEY.EDU (Mike (Don't have strength to leave) Meyer) Newsgroups: comp.unix.questions Subject: Re: UNIX file extensions Message-ID: <1919@jade.BERKELEY.EDU> Date: Sat, 13-Dec-86 02:31:51 EST Article-I.D.: jade.1919 Posted: Sat Dec 13 02:31:51 1986 Date-Received: Mon, 15-Dec-86 21:54:36 EST References: <92@vianet.UUCP> <1694@cwruecmp.UUCP> Sender: usenet@jade.BERKELEY.EDU Reply-To: mwm@eris.BERKELEY.EDU (Mike (Don't have strength to leave) Meyer) Organization: Missionaria Phonibalonica Lines: 29 In article <1694@cwruecmp.UUCP> cwruacm@cwruecmp.UUCP (Kronen Insultants) writes: > >I don't know if these are really enforced anywhere, but how about > > .el (or .ell) Lisp (probably Franz) source file I think Franz uses .l (been a long time since I looked). GNU Emacs uses .el for Elisp and .elc for compiled Elisp. It "enforces" this by looking for.el and .elc when asked to load . Similarly, Gosling/Unipress Emacs uses .ml for Mock Lisp files. For yet more, Scheme uses .scm and CLU uses .clu. I think the Arizona Little SmallTalk uses .st. Icon uses .icn. But for Unix, the point is kind of moot. The only "enforcement" is what certain application programs do with them. I've compiled pseudo-devices by symlinking them to "gort.c" in the current directory. Since such tricks will always work, and nothing in the OS enforces those typings (thank GOD!), what's the point of worrying about what the extensions are? Use the contents. Compress checks for them, and a file system browser I wrote back in the v6 days did the same kind of thing. Much more reliable. After all, EVERYONE knows that .s files are SLOGO source, right?