I agree with you that the way these paths are defined, is unclean. In general, for use in perl alone, I'd agree with your conclusion: to use forward slashes. However, this is not just perl: the paths are passed as parameters via OLE to Word. I cannot test my hyphotesis, but I seriously doubt whether Word would accept paths with forward slashes. From what I remember with my experience with OLE and Excel, a program from the same stable as Word, is that it was extremely unhappy about forward slashes in file paths: it only accepted backslashes as a valid directory separator.
Conclusion: using backslashes in the paths is more than justified here. However, the way they're used in writing down these strings, is still unclean.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|