In my understanding,
Intrepid was
rantingcomplaining about the quality of the warning message, which I find correct: the error message should be changed.
I'm no Microsoft advocate, but in this case I'd say that the problem isn't in the OS, but in the utilities. If something is technically supported, but used in the wrong manner, I wouldn't say that it doesn't really work. As PodMaster correctly points out, an application invoking the shell should quote its arguments to get them understood well; so, it's possible to use the feature without breaking anything.
This doesn't happen for ActiveState Perl, in which case the warning message should read "We have more interesting things to do other than fixing that spaces-in-paths issue in all stuff, so don't put spaces in your installation paths and you'll live happy".
Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')
Don't fool yourself.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.