× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



WDSC 7.0.0.8, Windows XP SP2

So I'm trying to write a regular expression that will allow me to search
for a specific PI and I've encountered two obstacles I can't find a way
around. Given:

dProcedureName...
d pi

* Update name in PERSON file
pProcedureName b
dProcedureName pi 10i 0
d parm like(parm_proto)

I'd like to search the entire source for ProcedureName. In a text file,
using the Eclipse plugin Regex Util, the following regex will find both
PI lines:

.{5}d\s*(ProcedureName)|\1\.\.\.\r\n.{5}d\s*pi

This does not work in WDSC for two reasons that I can see.

1) I cannot figure out how to formulate a search that spans lines, i.e.
dProcedureName...
d pi
What is WDSC using for a line terminator?
^.{5}d\s*ProcedureName\.\.\.$ catches the terminator, but neither \n nor
\r seem to. In no event can I seem to match the first line ending in
the ellipsis and also match the second line with the pi.



2) Capturing does not seem to work, i.e. \1 does not seem to reflect the
(ProcedureName) group. Not sure how to debug that, as I was trying to
use the 'or' in such a way that I didn't have to repeat typing the
searched-for subprocedure name.

Any ideas on overcoming either of these? For now, I'm giving up finding
the continued / ellipsis version and going with ^.{5}d\s*ProcedureName\s*pi
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.