This is some tweaky shit. If we fix it like Charles says it will fix this particular problem and probably match the windows C port, but at the cost of a bunch of libraries breaking because they are all written assuming unix-style separators. This is one aspect where Ruby could really give us direction or at least put their foot down and try and make Ruby more compatible across platforms. I personally think is wrong since it totally blows for things like Dir[] (let that sink in for a bit)...

Thomas E Enebo
added a comment - 27/Apr/10 11:49 AM This is some tweaky shit. If we fix it like Charles says it will fix this particular problem and probably match the windows C port, but at the cost of a bunch of libraries breaking because they are all written assuming unix-style separators. This is one aspect where Ruby could really give us direction or at least put their foot down and try and make Ruby more compatible across platforms. I personally think is wrong since it totally blows for things like Dir[] (let that sink in for a bit)...

Benoit Daloze
added a comment - 20/Apr/12 4:59 PM - edited Actually, File.join does not add \, and the RubySpec description is very misleading:
"joins parts using File::ALT_SEPARATOR on windows".
The RDoc documentation is simple: "Returns a new string formed by joining the strings using File::SEPARATOR." (File::SEPARATOR being always "/").
But the hidden behavior is MRI does keep the \ if they are present and do not insert '/'.
This does not seem to be tested in MRI test/
I wonder if this can be considered as a bug (Ruby is always returning paths with "/" when you give no \ ).
And I agree there should be some unification of the separator (which seems already the direction, but could be stricter).
I'll ask on ruby-core.

Charles Oliver Nutter
added a comment - 29/Dec/14 4:33 PM JRuby has moved bug tracking to Github, accessible via our Github page at https://github.com/jruby/jruby/issues , or via http://bugs.jruby.org . In addition, this bug has not been updated in over two years.
We have decided to close down these old JIRA issues.
If your report is still a problem on current JRuby versions (1.7.18 or master/9.0.0.0), please re-file the bug at http://bugs.jruby.org .
You can contact us on the JRuby mailing lists, Freenode IRC channel #jruby, or the @jruby Twitter account if you are unsure how to proceed.