Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!aplcen!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: ansi c and directories
Message-ID: <11707@smoke.BRL.MIL>
Date: 29 Nov 89 19:53:16 GMT
References: <225800244@uxe.cso.uiuc.edu> <3332@cbnewsd.ATT.COM> <7127@ficc.uu.net>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <7127@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>So, what should the first argument to fopen() be on an Unisys 1100?

A filename, whose mapping to file access is defined by the implementation.

X3J11 tried to identify a minimal "portable filename" subset for use in
applications as header file names.  There almost wasn't any common subset.
I think we figured out that five monocase alphabetics followed by ".h"
would be all that could be guaranteed across all the C implementation
environments we knew of, and there were problematic aspects of even such
a minimal guarantee.  That hardly seemed worth the trouble.