Home > Archive > PERL Miscellaneous > December 2005 > FAQ 5.34 Why can't I use "C:\temp\foo" in DOS paths? Why doesn't `C:\temp\
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
FAQ 5.34 Why can't I use "C:\temp\foo" in DOS paths? Why doesn't `C:\temp\
|
|
| PerlFAQ Server 2005-12-03, 3:56 am |
| This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
5.34: Why can't I use "C:\temp\foo" in DOS paths? Why doesn't `C:\temp\foo.exe` work?
Whoops! You just put a tab and a formfeed into that filename! Remember
that within double quoted strings ("like\this"), the backslash is an
escape character. The full list of these is in "Quote and Quote-like
Operators" in perlop. Unsurprisingly, you don't have a file called
"c:(tab)emp(formfeed)oo" or "c:(tab)emp(formfeed)oo.exe" on your legacy
DOS filesystem.
Either single-quote your strings, or (preferably) use forward slashes.
Since all DOS and Windows versions since something like MS-DOS 2.0 or so
have treated "/" and "\" the same in a path, you might as well use the
one that doesn't clash with Perl--or the POSIX shell, ANSI C and C++,
awk, Tcl, Java, or Python, just to mention a few. POSIX paths are more
portable, too.
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
| |
| Purl Gurl 2005-12-03, 3:56 am |
| PerlFAQ Server wrote:
> Either single-quote your strings, or (preferably) use forward slashes.
> Since all DOS and Windows versions since something like MS-DOS 2.0 or so
> have treated "/" and "\" the same in a path,
Absolutely false. This is another example of a Perl FAQ promulgating
totally bogus information.
This FAQ is mondo beyondo stupid.
Purl Gurl
| |
| brian d foy 2005-12-18, 7:57 am |
| In article <m27jamg1j4.fsf@Sherm-Pendleys-Computer.local>, Sherm
Pendley <sherm@dot-app.org> wrote:
> PerlFAQ Server <comdog@pair.com> writes:
>
[color=darkred]
> Isn't it time to update the "DOS paths" and "legacy DOS filesystem" bits?
> Windows hasn't been built on top of MS-DOS, or used FAT16, for quite a long
> time now.
It's been time for a while, but nobody has done it. Don't wait for me; I
don't use Windows. :)
--
brian d foy, bdfoy@cpan.org
Subscribe to The Perl Review: http://www.theperlreview.com
| |
| brian d foy 2005-12-18, 7:57 am |
| In article <m23blag1el.fsf@Sherm-Pendleys-Computer.local>, Sherm
Pendley <sherm@dot-app.org> wrote:
> PerlFAQ Server <comdog@pair.com> writes:
>
>
> Oh, and one more kvetch - this question goes all the way out to column 86.
All of the questions are on a single line. To wrap them we'd have to
rewrite a lot of the tools that deal with the perlfaq (probably
involving a much more complicated parser).
The trick is to come up with shorter questions.
--
brian d foy, bdfoy@cpan.org
Subscribe to The Perl Review: http://www.theperlreview.com
|
|
|
|
|