Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 24 Jan 2000 22:02:47 -0500
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Trapping the Win32 API path functions
Message-ID: <20000124220247.A5855@cygnus.com>
Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i

It has occurred to me that we could trap the Win32 functions
which understand paths and slip Cygwin style paths in there.

At the most trivial, we could make a front-end for kernel32.dll
although I'm sure it wouldn't be that easy.

That would allow much greater functionality for non-cygwin
applications.  So, you could do something like:

notepad /etc/termcap

or

javac //d/foo/var.j

(Hmm.  I wonder why I thought of that example)

Is this crazy?  Anyone interested in doing this?

cgf