This core dumps on 5.8.3 - I dunno if upgrading can be classed as a solution :-)
Update: Oh, and perlre (on 5.8.3) says:
"(?{ code })"
WARNING: This extended regular expression feature is considered highly experimental, and may be changed or deleted without notice.
I think exploding satisfies the whole "highly experimental" bit.
There is however a simple way of making the code work: you have too many question marks. Try:
print "$_ ", /(.*)(?{$countSpaces->()})/ ? "has 1 or no spaces\n" : "h
+as more than one space\n";
...in the right place. The output is:
this line has more than one space
has more than one space
that_is_5_spaces
has more than one space
This isonespaceonly
has more than one space
therearenospaceshere
has 1 or no spaces
...which looks like (almost) the right output to me.
Update 2 Erm, ah. Doh. (??{ code }) is perfectly valid according to perlre too - put equally experiment. Nevermind. Using highly experimental features is probably a bad idea.
If the information in this post is inaccurate, or just plain wrong, don't just downvote - please post explaining what's wrong.
That way everyone learns.
-
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.
|