While searching for information on the idiosyncrasies of Windows command line processing, I came across this article by Daniel Colascione:


It's a fairly long article - Microsoft really made a mess of this, but it's now a long-standardized mess so it can't be fixed without breaking millions of programs.

Anyway, down at the bottom of the article are some footnotes:

You must login to post a comment.
Loading comment... The comment will be refreshed after 00:00.

Be the first to comment.