Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re^4: Error triggered with Nested quantifiers in regex

by anakin30 (Acolyte)
on Aug 25, 2010 at 03:33 UTC ( #857068=note: print w/replies, xml ) Need Help??

in reply to Re^3: Error triggered with Nested quantifiers in regex
in thread Reaped: Error triggered with Nested quantifiers in regex

previously the suggestion/advice was to change (m/^de.e++ ) to (m/^de\+\+), is this valid?

i couldn't find any lines (m/^de.e++) in the code so how am i gonna change it to (m/^de\+\+)

can you please explain in details

Thanks to you

  • Comment on Re^4: Error triggered with Nested quantifiers in regex

Replies are listed 'Best First'.
Re^5: Error triggered with Nested quantifiers in regex
by suhailck (Friar) on Aug 25, 2010 at 04:35 UTC

    421                if ($mail && ($mail =~ /^$edsMail$/i)) {

    Whats the value of $edsMail ??

      the value is

      thanks for your reply

      i really appreciate it much

        try changing




Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://857068]
[ambrus]: Corion: well Prima::Object says something like that the cleanup method will send an onDestory message and that you can't get more messages after cleanup, or something.
[Corion]: ambrus: Yeah - I don't think the deep source dive will be necessary if things are implemented as simple as they could be :)) And hopefully I won't need (more) timely object destruction. I can update the screen at 60Hz and hopefully even do HTTP ...
[Corion]: ... transfers in the background. Now that I think about it, this maybe even means that I can run the OpenGL filters on Youtube input :)
[ambrus]: Corion: I mentioned that the unix event loop of Prima always wakes up at least once every 0.2 seconds. Have you found out whether the win32 event loop of Prima does that too?
[Corion]: ambrus: Hmm - I would assume that the onDestroy message is sent from the destructor and doesn't go through the messageloop, but maybe it is sent when a window gets destroyed but all components are still alive...
[ambrus]: Corion: partly deep source dive, partly just conservative coding even if it adds an overhead.
[Corion]: ambrus: Hmm - no, I haven't looked at wakeup intervals ... I wonder why it should want to wakeup periodically because it gets a lot of messages from the Windows message loop (on Windows obviously)
[ambrus]: (Alternately a deep source dive and then rewrite that event loop to make it better, and then as a bonus you get an idle method.)
[ambrus]: The 0.2 seconds wakeup is likely a workaround for some bug, but I can't guess what bug that is.
[ambrus]: It's been there since Prima 1.00 iirc

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (8)
As of 2016-12-09 10:31 GMT
Find Nodes?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:

    Results (150 votes). Check out past polls.