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


  1.  Home
  2. MIDRANGE-L
  3. July 2006

Re: Alternative to QCLSCAN?
THANKS, I found your articles. I don't think this will work for me on the surface. Basically I need to take the list of files from the directory and process them one of two different ways. If the file matches the "*.xls" pattern then it is copied to the destination with a different user-specified filename. If it does not match, it is simply copied to the destination folder. 

Ex: Pattern to match: *Info.xls
     20060701Info.xls  -->  InfoDoc.xls
     XYZSmile.xls      -->  XYZSmile.xls
I noticed that RegEx provides an "opposite" match type of thing by using the ^ within a set []. Does it provide something to 'reverse' the entire thing? So I could do one Dir read using ".*xls$". And then another one using something like NOT ".*xls$". 

Thanks,
   Scott J.


Scott Klement wrote:

Is there an alternative to the QCLSCAN API?  I need to scan incoming
filenames from the readdir IFS API for matches to things like "*.xls".
QCLSCAN does not allow the "*" in the first spot.
I solved this by using the regular expression APIs. Granted, they don't allow you to use '*.xls', but they'd let you accomplish the same thing with '.*xls$'
I've written articles that demonstrate combining the regular expression APIs with the IFS APIs, as well as wrappers that make them available from CL programs. If you're interested, let me know, and I'll dig up links to the articles.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.