[HACKYSTAT-DEV-L:241] Re: [CSDL-LOCAL-L:57] expanding pattern matching in reduction functions

[Philip Johnson]

I have two thoughts:
1. Mike, is there any reason why the following approach wouldn't suffice 
for your HPC needs?

ActiveTime("**/*.h") + ActiveTime("**/*.c").
2. If there's some reason that the current approach wouldn't be OK, then I 
would propose that we embed the "or" into the FilePattern string itself:

ActiveTime("**/*.c, **/*.h, **/*.cc")
This means that all of the mechanism occurs inside of FilePattern, which 
seems like the appropriate place to deal with it.  It also implies that ',' 
cannot be part of a file name (which seems ok to me).

Cheers,
Philip
p.s. I'm replying to hackystat-dev-l, not csdl-local-l, since this is a 
hackystat design question.

--On Thursday, November 4, 2004 3:56 PM -1000 "(Cedric) Qin ZHANG" 
<[EMAIL PROTECTED]> wrote:

Hi,
Mike mentioned to me today that he (and Philip?) wants to have a pattern
that could match both c and h files at the same time. In current
implamentation you  can only match either c or h files. If you want to
have total active time on both c and h files, then you have to use:
ActiveTime("**/*.h") + ActiveTime("**/*.c").
It seems that people prefer to something like
   ActiveTime("**/*.h + **/*.c").
This is doable, but we need to decide operator it should support and the
syntax we want to use.
What I can think is:
   * Operator: OR(+), NOT(!)
   * Syntax: pattern1 + pattern2, !pattern1, !pattern1 + pattern2
Should we allow more complex syntax? If so, what's the advantage?
Any comments, please.
Thanks.
Cedric