× 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.



Rick,

The others beat me to the punch. You might check out
http://regexlib.com/


Regards,
Pat Landrum
Senior Programmer/Analyst
Hanover County Public Schools
200 Berkley Street
Ashland, Va 23005
Phone: 804-365-4658 Email: plandrum@xxxxxxx


Notice: This message or any accompanying documents may contain
confidential or privileged information of Hanover County Public Schools.
If you are not the intended recipient, disclosure, copying or
distribution is strictly prohibited by state and federal law. If you
received this message in error, please notify the sender as soon as
possible.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Monday, May 03, 2010 3:29 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: File name regular expression

Thanks Dennis. That was it. I kept the original expression and just
inserted a * after [A-Z0-9].

I have a question (or two) about your expression.

1) I re-read the wikipedia site and I get the * after [A-Z0-9], but I
don't get the * at the end. Shouldn't that be $ to look for .xml at the
end of the name?

2) If the parenthesis are removed does ^ and $ still match the pfi_ and
.xml strings respectively or just a single character?

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Monday, May 03, 2010 1:59 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: File name regular expression

I am attempting to match a file name pattern to file names read from
an IFS directory. What I want is the pattern pfi_nnnn.xml. The files

I want will begin with 'pfi_', and end with '.xml'. Currently there
are 10 digits in between but I wanted to be able to handle varying
numbers.
My expression compiles ok but it doesn't match the file names. Doing
more research on the web makes me think I'm pretty close but hasn't
given me clear direction about the use of the '^' and '$' symbols for
matching the beginning and end of a string. In particular, the end of

a string. I am attempting to match '.xml' using (.xml)$. My reading
has me wondering if $ only matches the last character and not multiple

characters. Hopefully someone on the list can help me out with this.
I am posting my current expression below.


^(pfi_)[A-Z0-9](.xml)$

You're so close!

I would do ^pfi[A-Z0-9]*.xml*. There's no advantage that I see so your
parentheses.

(It's the missing splat that's killing you now.)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Hard work pays off in the future. Laziness pays off now.



Privileged and Confidential. This e-mail, and any attachments there to,
is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any dissemination,
distribution or copying of this e-mail and/or any attachments thereto,
is strictly prohibited.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.