Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-Id: <4.1.20000612171519.01ecc4d0@pop.mathworks.com> X-Sender: paulk@pop.mathworks.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 12 Jun 2000 17:25:45 -0400 To: Carl Thompson From: Paul Kinnucan Subject: Re: Make and javac compliler problem in bash Cc: Cygwin List In-Reply-To: <394550B8.905A1B35@carlthompson.net> References: <4.1.20000612123820.01ed6a10@pop.mathworks.com> <4.1.20000612154844.01ed33d0@pop.mathworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:06 PM 6/12/00 -0700, Carl Thompson wrote: >Paul Kinnucan wrote: > >> ... > >> >> How could it be otherwise? The Windows version of javac is, >> >> surprise, a Windows application. Windows applications don't >> >> recognize Unix paths. Ergo, the Windows version of javac does not >> >> recognize Unix paths. QED. >> > >> >Actually, Win32 _does_ allow path names to use forward slashes as the >> >directory separator. The FAQ question you pointed out above even >> >mentions >> >> But not to BEGIN a path as in Jin's example. > >That's certainly not what you wrote above, is it? Nor is it true. There is >nothing inherent in Win32 that says it can't use paths that begin with a "/" >. Try pulling up a command prompt and type > > notepad /path/to/a/file This is simply a shorthand for currentdrive:/path/to/a/file. If you want to call this a Unix path, fine. I call it a pseudo Unix path of limited utility. I think it's misleading to generalize from this that some Windows applications accept Unix paths. In so doing, you're obscuring what's really going on and implying capabilities that do not exist. - Paul -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com