RE: bash, javac and that pesky slash.

["Halim, Salman" <salman@bluestone.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]

java contains a File object which contains two static fields, one for path
separator and one for a directory separator.  on windows, they end up being
; and \. . .

perhaps this has something to do with the issue at hand?  (probably not; the
classpath is set and used elsewhere)  however, it would make sense for a
native application to be designed to work off the native settings.  cygwin's
settings aren't native to the windows environment :)

--
   =========================================================
   Salman Halim                 Technical Support           
                                                            
   Bluestone Software           Phone:  (856) 727-4600      
   1000 Briggs Rd.                                          
   Mt. Laurel, NJ 08054         Email:  salman@bluestone.com
   =========================================================
   Would you  care for a drink?   I mean, if it  were, like,
   disabled and you had to look after it?


> -----Original Message-----
> From: Andre Oliveira da Costa [ mailto:costa@cade.com.br ]
> Sent: Monday, January 24, 2000 2:53 PM
> To: cygwin@sourceware.cygnus.com
> Subject: RE: bash, javac and that pesky slash.
> 
> 
> > -----Original Message-----
> > From: cygwin-owner@sourceware.cygnus.com
> > [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of 
> David Robinow
> > Sent: Monday, January 24, 2000 5:03 PM
> > To: cygwin@sourceware.cygnus.com
> > Subject: RE: bash, javac and that pesky slash.
> [...]
> >  The "Therefore," above is incorrect.  There are
> > plenty of non-cygwin apps that recognize '/' as a path
> > seperator.
> 
> True. That was a (too) strong assumption. Thanks for pointing 
> that out.
> 
> [...]
> > > CLASSPATH environment variable
> > > must use M$-path-style also, because it is meant to
> > > be interpreted by jdk tools.
> >  Could be, I know nothing at all about java/jdk.
> 
> Believe me, it is: I recently installed jdk-1.2.2 on my NT4 
> machine, and
> Java tools refused to work from my bash prompt because I had CLASSPATH
> defined on my .bashrc with UNIX-like pathnames separated by 
> ":". When I
> changed it to M$-style paths and ";" among pathnames, it all worked.
> 
> Regards,
> 
> Andre
> --
> André Oliveira da Costa
> (costa@cade.com.br)
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com