Xref: utzoo comp.lang.c:11794 comp.os.vms:7956 Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mit-eddie!bbn!uwmcsd1!ig!agate!labrea!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!cernvax!hjm From: hjm@cernvax.UUCP (hjm) Newsgroups: comp.lang.c,comp.os.vms Subject: Re: cpp compatiblity Unix/VMS Keywords: cpp #include VMS Message-ID: <792@cernvax.UUCP> Date: 10 Aug 88 07:58:04 GMT References: <134@iquery.UUCP> <318@laic.UUCP> Reply-To: hjm@cernvax.UUCP () Followup-To: comp.os.vms Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland Lines: 22 #include foobar #includeare not the same if foobar is a logical name! Using logical names allows for greater flexibility in where include files are kept (you may not want them kept with all the others because of a name conflict, or perhaps you just want to be tidy), whereas the form is an absolute address. I have spent a lot of time reorganising disks after several head-crashes and logical names were easy to change to different locations, but changing absolute addresses which referred to files by disk and directory were *much* more troublesome. If you don't have the source for a program, then try to find out what files it accesses and where, and then change it without logical names. I'm redirecting followups to comp.os.vms as this is a VMS issue, and not a lot to do with C (thank god!). Hubert Matthews