Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"David P. Caldwell" <inonit AT inonit DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: javac on cygwin
Date:	Mon, 6 Jan 2003 10:32:57 -0500
Message-ID:	<JIEPJODHFFPGJDGMCPBEEEHMEDAA.inonit@inonit.com>
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.44.0301060934260.10883-100000@slinky.cs.nyu.edu>

Igor:

>Actually, the custom java.io.File wrapper is very useful in that it's
>orthogonal to the purpose of my scripts and takes care of one of the
>caveats (namely, the filenames passed to Java programs).

Actually, the way it works now, the programs I write have to be Cygwin-aware
(I don't have a java.io.File substitute -- I have an inonit.cygwin.File
class which can represent a Windows or UNIX-style path).

However, as you mention, it's at least occurred to me that the entire
java.io.File class could be re-implemented with Cygwin-aware functionality
and then could be used in preference to the java.io.File class by putting it
in front of rt.jar in the -bootclasspath (at least on JDK 1.2 and later).

One would probably also have to change FileInputStream and other classes --
I haven't looked into it extensively.

-- David.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -