X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112262035.AA17878@clio.rice.edu>
Subject: Re: lfn from scratch...
To: eliz AT is DOT elta DOT co DOT il
Date: Wed, 26 Dec 2001 14:35:22 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <3942-Wed26Dec2001220719+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Dec 26, 2001 10:07:19 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > I always assumed UNCs were not supported at all.
> 
> That's about right.  As soon as a UNC gets taken apart by library
> functions, like to find the drive letter, we fail.  If the UNC goes
> directly to the system call, it will usually work, at least on
> Windows.

Yes, I think this is what I see.

> > Should we fix this?
> 
> It's not clear to me how to fix this.  We should either augment those
> library functions which tinker with file names to know about UNCs, or
> write code to map between a UNC and a drive letter.  

For most of the cases I'm interested in - there is not a drive letter
mapping - its just a name like \\cws333\c$\djgpp ...

I would need to think about this - we would need to recognize UNCs as
being driveless and handle specially.  You can't CD to them, just
open files, do file I/O ... Humm...

Thanks for the thoughts.