[
https://issues.apache.org/jira/browse/IO-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601365#action_12601365
]
Stephen Colebourne commented on IO-171:
---------------------------------------
The best approach to this issue may simply be better documentation of the
assumptions of IOCase. Trying to make it too clever is likely to cause
problems, especially as we don't have direct access to many OS.
> 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.
