david wrote:
The Perl book (I think it's the Programming Perl) has an example where a certain reg. exp and string combination can make Perl's reg. engine run forever (in terms of years!) because of backtracking. The solution the book generally recommand is to use one of the newer reg. exp extension with positive, negative look ahead, etc. You might want to check it out. Since you are letting user directly entering their reg. exp., the above probably won't work. Why not just time out the reg. exp if it's taking longer than you allow? For example, you can time out the match if it's taking longer tank 3 seconds? This method is used quit extensively when people want to time out slow system calls.thanks david.
yeah, i think i'll use the OS facilities for this. i was initially hoping for a predictive/preventive solution (like a regexp analyzer or Safe.pm-for-regex-language or something). but OS-based solution is also fine with me.
--
dave
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
