Date: Sun, 16 May 1999 17:22:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Frank Heckenbach <frank AT tim DOT gerwinski DOT de>
cc: djgpp-workers AT delorie DOT com
Subject: Re: realpath()
In-Reply-To: <53B0C02D.19990516141508.FOO-155E.frank@goedel.fjf.gnu.de>
Message-ID: <Pine.SUN.3.91.990516171930.20684D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 16 May 1999, Frank Heckenbach wrote:

> :        Otherwise   it  returns  a  NULL  pointer  and  places  in
> :        resolved_path the absolute pathname of the path  component
> :        which  could not be resolved.

This is not very specific, and in fact I could interpret this in several 
ways.  Could you please throw together a short test program and see what 
it does with non-existent file names?

> However, I don't actually need this behaviour. I thought it was part
> of the "standard" functionality of realpath(), but if it isn't on
> other systems, you probably don't need to implement it on DJGPP.

When we have a test program, we could run it on different platforms and 
see what it returns.  Then we could decide what to do in the DJGPP 
version.