Hi Bruce, If you change your mind, your assistance would be most welcome. The Google group would be a good place to finish up the pcrecpp wrapper, it has a large area for file sharing, plus using it would spare disinterested readers from exposure to the subject matter. Julien, Sean, Alan C and myself are there.
> One thing I have always wondered. It seems most of the issues have > to do with matching multi-line stuff where the end of line indicator > is \r\n. I think you have confused the (not fully realized) enhancements in recent PCRE releases + the test plugin vs. the limitations of the current and test plugin. The important things we are lacking are, the ability to pass options to PCRE, the ability to reliably use lookbehinds (including ^, which is a form of lookbehind) in global operations, and meaningful results involving empty matches in global operations. These issues stem from using pcre's posix api instead of the native api, and they exist regardless of the line ending used in the input string. BTW, in the previous thread suggesting compiling PCRE functions directly into PowerPro (where you said it would be useless except for minor performance gain), would it not solve the entire issue of exported/imported variables (including vectors)? Regards, Sheri
