commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-171) IO assumes there are only two OSes: Windows and Unix
Date Fri, 30 May 2008 14:50:45 GMT

    [ https://issues.apache.org/jira/browse/IO-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601155#action_12601155
] 

Niall Pemberton commented on IO-171:
------------------------------------

> The problem with the current behaviour on VMS is that the implicit (default) choice is
not guaranteed to be correct.

OK well I gave my opnion - "from my PoV that doesn't add anything to IO or help OpenVMS users
- as it stands currently it doesn't work for OpenVMS users who wants "case-insensitive" -
with that kind of change it doesn't work for ALL OpenVMS users - plus it messes up any existing
OpenVMS users who have been relying on the current behaviour." If you want to change the JavaDoc
to put a note about OpenVMS, thats fine by me - personally I'm against throwing the exceptions
since it adds unecessary additional complexity that solves nothing for no-one. OpenVMS users
need to choose the correct IOCase flavour they want to use and understand the implications
of such in their enviroment.

> There is still the general problem that the separator character and case-sensitivity
are not related in any way.

Why should they be? I don't see any problem with FilenameUtils.SYSTEM_SEPARATOR on OpenVMS
and I don't see any reason why the separator character should be linked to case sensitivity
of file names. To be honest, just saying "theres is still the general problem..." is too vague
- please be specific about actual problems in Commons IO and what you propose should be done
about it.

> IO assumes there are only two OSes: Windows and Unix
> ----------------------------------------------------
>
>                 Key: IO-171
>                 URL: https://issues.apache.org/jira/browse/IO-171
>             Project: Commons IO
>          Issue Type: Bug
>            Reporter: Sebb
>            Priority: Minor
>
> Just noticed that IO assumes systems are either:
> Windows-like:
> * File.separatorChar = \
> * Case-insensitive matching
> or
> Unix-like:
> * File.separatorChar = /
> * Case-sensitive matching
> It may well be true that there are only two different file sepator characters, but it
is not true that all non-Windows systems use case-sensitive matching.
> For example, OpenVMS uses a file separator char of /, but originally only supported case-insensitive
file names (always shown as uppercase).
> Current versions of OpenVMS support both upper and lower-case; the default is to use
case-insenstive matching (and upper case names).
> Perhaps the IOCase.SYSTEM constant needs to have an "Unknown" or "Variable" setting for
this; it would then be an error to use IOCase.SYSTEM to determine the case sensitivity.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message