Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
Message-ID: <3BC6103E.5090800@arielpartners.com>
Date: Thu, 11 Oct 2001 17:33:50 -0400
From: Craeg K Strong <cstrong@arielpartners.com>
Organization: Ariel Partners LLC
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4) Gecko/20010915
MIME-Version: 1.0
To: ant-dev@jakarta.apache.org
Subject: Re: disregard my FileUtils patch
References: <sbc5ab8f.075@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jeff Tulley wrote:

>Now, I'm wondering about some basic functionality here that I might be misunderstanding.  Are resolveFile and normalize supposed to be able to handle all three types of file system names, "/usr/bin", "c:\temp", and "sys:/tmp" while executing on any given system, or is it ok for "sys:/tmp" to be handled only when executing on NetWare, or "c:\temp" to be handled when executing on Windows, etc?  If I need to handle everything on every system, then I'll have to refactor resolveFile and normalize a whole lot more.  The going assumption used to be that if it contained a ":" as the second character, that was automatically a windows path.  Things get a little more complicated for general support if that colon can move to later in the string and still represent a valid "drive" name.(really, a NetWare volume).
>
One case you may not have considered is that of emulation environments: 
 Under Cygwin in
Windows, one can use UNIX-style file system names.  Cygwin is quite 
popular, but I
am sure there are other such environments (for example, VMware)....

HTH,

--Craeg