Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3DFE4B7F.1F46D3BD@phekda.freeserve.co.uk>
Date: Mon, 16 Dec 2002 21:54:07 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: proposed putpath.c patch
References: <10212152352 DOT AA21607 AT clio DOT rice DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Charles Sandmann wrote:
[snip]
> At the bottom is my diffs for the _put_path documentation.  Comments?
[snip]

Shouldn't it be @file{x:} rather than @var{x:}? x: isn't a variable for the
function. I don't think you need @file{@var{x:}<whatever>}. I think
@file{x:<whatever>} will do. Or was @var{} the right way to do this, before
@file{} was added to texinfo?

I'd like to try building fileutils with the patch applied, but I don't know
when I will get round to it. I also wonder how much slower it will be for the
cases mention.

> *** putpath.tx_ Wed May 12 04:36:52 1999
> --- putpath.txh Sun Dec 15 17:22:44 2002
> *************** scripts.
> *** 56,64 ****
>   Any file name which begins with @file{/dev/} or @file{@var{x:}/dev/}
>   (where @var{x:} is any valid DOS drive letter) has the @file{/dev/} or
> ! @file{@var{x:}/dev/} prefix removed, and the rest is passed to DOS.
>   This is because some DOS functions don't recognize device names unless
>   they are devoid of the drive and directory specifications, and programs
>   could add a drive and a directory if they convert a name like
>   @file{/dev/con} to a fully-qualified path name.
> 
>   @item @file{/dev/x/} is translated into @file{x:/}.
> --- 56,70 ----
>   Any file name which begins with @file{/dev/} or @file{@var{x:}/dev/}
>   (where @var{x:} is any valid DOS drive letter) has the @file{/dev/} or
> ! @file{@var{x:}/dev/} prefix removed (if the @file{/dev/} directory does
> ! not exist), and the rest is passed to DOS.
>   This is because some DOS functions don't recognize device names unless
>   they are devoid of the drive and directory specifications, and programs
>   could add a drive and a directory if they convert a name like
>   @file{/dev/con} to a fully-qualified path name.
> + Because of the different behavior when the @file{/dev/} directory
> + exists, you should only add the prefix @file{/dev/} to your DOS device
> + names if necessary and be sure that the @file{/dev/} does not exist.
> + Due to the additional overhead of checking if @file{/dev/} exists,
> + functions working with DOS device names with the prefix will be slower.
> 
>   @item @file{/dev/x/} is translated into @file{x:/}.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]