Re^9: Find Prefix if regex didn't match

in reply to Re^8: Find Prefix if regex didn't match
in thread Find Prefix if regex didn't match

Your benchmarks are not exactly what I thought about, what I have in my mind is:

I see :)

But, still, neither results seems very important , network is always much slower than both

Comment on Re^9: Find Prefix if regex didn't match Download Code

Replies are listed 'Best First'.
Re^10: Find Prefix if regex didn't match by demoralizer (Beadle) on Nov 07, 2012 at 06:31 UTC
But, still, neither results seems very important , network is always much slower than both Yes, that's for sure meanwhile... in a previous versions I used `$rec = <$term>` instead of `read($term, $rec, 0xFFFF)` what came in my mind when I was writing one of my replies here and what definitely was the major reason for my timing problem because the log file I receive via TCP contains many new lines what caused much more matchings than necessary... so asking questions here has already fulfilled its purpose :) But what has left, there is still a problem in my mind I haven't really solved yet, that is scanning for prefixes which could be a regular expression, not just a simple ASCII string. So I'm still wondering if there is really no possibility in pearl asking the regexp engine to tell me at which position it started matching when it reached the end of given string the first time even if it hasn't reached end of expression yet... By the way many thanks for all your help, according to your astonishing response time I guess you live in front of your computer? ;)	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^10: Find Prefix if regex didn't match
by demoralizer (Beadle) on Nov 07, 2012 at 06:31 UTC

But, still, neither results seems very important , network is always much slower than both

Yes, that's for sure meanwhile... in a previous versions I used $rec = <$term> instead of read($term, $rec, 0xFFFF) what came in my mind when I was writing one of my replies here and what definitely was the major reason for my timing problem because the log file I receive via TCP contains many new lines what caused much more matchings than necessary... so asking questions here has already fulfilled its purpose :)

But what has left, there is still a problem in my mind I haven't really solved yet, that is scanning for prefixes which could be a regular expression, not just a simple ASCII string. So I'm still wondering if there is really no possibility in pearl asking the regexp engine to tell me at which position it started matching when it reached the end of given string the first time even if it hasn't reached end of expression yet...

By the way many thanks for all your help, according to your astonishing response time I guess you live in front of your computer? ;)

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom