Date: Wed, 1 Oct 1997 10:58:09 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: eyal DOT ben-david AT aks DOT com
cc: csrabak AT dce03 DOT ipt DOT br, djgpp AT delorie DOT com
Subject: Re: libc functions handling of UNCs
In-Reply-To: <42256522.006048AC.00@aks.com>
Message-ID: <Pine.SUN.3.91.971001105749.10422C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 30 Sep 1997 eyal DOT ben-david AT aks DOT com wrote:

> Yes !.  MSVC 5 fails to print the long name.  Borland and Watcom print
> argv[0] correctly.

The startup code in Watcom/Borland probably converts argv[0] to the
long name, because Windows always passes the short alias, or so I'm
told.

> There is a Win32 API function that return the long file name.

We also have such a function: it's called `_truename'.

> I do not know why it is not used also for argv[0] -- strange.

It's probably very simple: the Exec function in Windows 95 wasn't
extended to handle long names.  If so, it just doesn't have enough
space to handle 260-long pathname.