Message-ID: <34F50F37.1F69@post.comstar.ru> Date: Thu, 26 Feb 1998 09:44:07 +0300 From: Dim Zegebart Reply-To: zager AT post DOT comstar DOT ru Organization: Comstar Ltd. MIME-Version: 1.0 To: Eli Zaretskii CC: DJGPP Mail List Subject: Re: Funny thing with _fixpath References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Precedence: bulk Eli Zaretskii wrote: > > On Wed, 25 Feb 1998, Thomas Demmer wrote: > > It is NOT undocumented. The docs says that the drive letter is > prepended, so the length is not preserved. It should have said that the > current directory is also added. Perhaps, my english is a problem :( Here is part of info file with description of _fixpath function, I can't see any words about adding full path of WORKING directory to the file name : >>> This function canonicalizes the input path IN_PATH and stores the result in the buffer pointed to by OUT_PATH. The path is fixed by removing consecutive and trailing slashes, making the path absolute if it's relative, removing "." components, collapsing ".." components, adding a drive specifier if needed, and converting all slashes to '/'. DOS-style 8+3 names of directories which are part of the pathname, as well as its final filename part, are returned lower-cased in OUT_PATH, but long filenames are left intact. _preserve_fncase, for more details on letter-case conversions in filenames. >>> -- ____ ____ | \ / Dim Zegebart ____/____ Moscow Russia WWW - http://www.geocities.com/siliconvalley/pines/7817 DZcomm - comm library for Allegro Palantir - multytasking kernel for Allegro (based on PDMLWP)