Greywolf <greywolf@starwolf.com> writes:

> Um, something I just noticed.  HFS+ filesystems.
>
> I haven't played with it much in a LONG time, but the last time I did
> anything with an HFS filesystem, the '/' character was valid in a
> filename.  How did we work around this?

Darwin, at least, works around this by swapping '/' and ':' (the
latter being the HFS path separator) in the VFS; OS X then swaps them
back when emulating the classic Mac API's.

Oh, other random Darwin/HFS+ note: attempts to create a file with a
name that is not a valid UTF-8 string return EINVAL, and valid file
names seem to be automagically normalized (e.g. a letter with an
accent gets broken into the letter and the accent, I guess for
collation purposes).

--Jed, having found this out the hard way by trying to have a file
  named after a CDDB entry that was in Latin-1 and had high chars.

-- 
#!/usr/bin/perl -- ## "But life wasn't yes-no, on-off.  Life was shades of gray,
sub f{(($n,$d,@_)=@_)?(substr(## and rainbows not in the order of the spectrum."
" ExhortJavelinBus",$n&&$d/$n,1),$n?f($d##   -- L. E. Modesitt, Jr., _Adiamante_
%$n,$n,@_):&f):("\n")}print f 1461,10324,55001,444162,1208,1341,5660480,79715997