First you rant atcomplain about how confusing that error message is. Then you provide examples that demonstrate what it is talking about.
Microsoft claims that spaces in filenames are supported. However many utilities including ones that you can get from Microsoft will break on spaces in filenames. And in the end you'll probably find that relying on what is technically supported (but effectively doesn't really work) to be a bad idea that is not worth it.
Furthermore I would submit that it is unreasonable to expect utilities to work in a case where the installation program just told you that they likely won't work. If you dislike it, those utilities are mostly drawn straight from the core Perl distribution, patches are welcome.
UPDATE: Rant was too strong a word. Complain fits better. Also I should note that I don't recall any arguments with Intrepid in chatter in recent months. Finally I should point out that I don't call a feature supported unless it both works and works with all supporting utilities that I'd expect people to use. The error message suggests to me that whoever wrote it has the same opinion that I do, and further thinks that, Microsoft's claims notwithstanding, spaces in filenames aren't really supported.
In reply to Re: The Evil Embedded Space
by tilly
in thread The Evil Embedded Space
by Intrepid
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |