Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!nosc!ucsd!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: conditional includes
Keywords: files, directories
Message-ID: <9450@smoke.BRL.MIL>
Date: 20 Jan 89 15:21:34 GMT
References: <8000011@modcomp> <334@twwells.uucp> <306@lakesys.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <306@lakesys.UUCP> chad@lakesys.UUCP (D. Chadwick Gibbons) writes:
>In article <334@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes:
>|There is also the little gotcha of identity: should foo and ./foo be
>|considered the same file? How about on a non-Unix system?
>	Actually, I would think they are considered the same file.  Yes,
>	even on non UNIX systems.

Nope.  There are systems where "./foo" is a valid filename but has
nothing to do with a file named "foo" and nothing to do with directories.

Systems that conform to IEEE Std 1003.1 (POSIX) will assign the usual
UNIX meaning to the "./" part of such a filename, and others may at
their discretion, but not all C environments are POSIX environments.