Chris, your explanation is correct, but ... AFAIK mono aims to be 100% compatible with .NET which is running on a case-insensitive environment.
I agree it is not a bug, simply different behaviour. However if my assumption "targeted at 100% compatibility" is correct, not only should mcs be "fixed" but also should mono. Eventough I can't imagine a really clean solution, it should be given some thought . Alexander On Wednesday 08 January 2003 06:02, Chris Ball wrote: > >> On 08 Jan 2003 01:21:59, Pablo Baena <[EMAIL PROTECTED]> said: > > I have a Classpath.dll on Windows. I compile the program with: mcs > > /r:classpath chachacha.cs which ends successfully. Then when I run > > the prog in Linux, mono fails because it doesn't find classpath.dll, > > and this is solved renaming the dll, but this is just annoying. > > The distinction occurs because vfat is a case-insensitive filesystem and > Unix filesystems aren't. If mcs was made case-insensitive, what would > happen if Classpath.dll was present _as well as_ classpath.dll on a Unix > filesystem? > > Personally, I don't believe the current behaviour to be buggy - more a > representation of the environment - nor able to be ``fixed'', whatever > that would entail. > > - Chris. -- Linux is like a wigwam, no windows, no gates and an apache inside _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
