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 })"I think exploding satisfies the whole "highly experimental" bit.
WARNING: This extended regular expression feature is considered highly experimental, and may be changed or deleted without notice.
There is however a simple way of making the code work: you have too many question marks. Try:
...in the right place. The output is:print "$_ ", /(.*)(?{$countSpaces->()})/ ? "has 1 or no spaces\n" : "h +as more than one space\n";
...which looks like (almost) the right output to me.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
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.
In reply to Re: Re: Why am I get a core dump when I use ??{}
by BazB
in thread Why am I get a core dump when I use ??{}
by Plankton
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |