Personally, I've avoided relying on unicode/charset semantics with regular expressions. Most of the input I deal with is either Latin-1 or some other "near IBM-ASCII" single byte encoding, and so is my source code. I've made my regular expressions lenient in the sense that I use dots where I expect umlauts.
Of course, if I were more strict about the encodings of my input data, or Perl were more smart about guessing the encoding of my input data (which is hard without carrying a dictionary of likenesses), I could write my source code and my regular expressions in unicode, and then it would be cool if \w would use the unicode semantics.
I have no opinion on \d, as German has only 0-9 as digits anyway, and my input data also.
-
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.
|