Hide Forgot
Description of problem: Unlike pretty much every other PCP client / component, pmie(1) does not seem to accept "s" denoting seconds. This is obviously not critical but would be nice for consistency.
Marko, in which context are you looking for "s" as an abbreviation? It works on the command line (-t, -S, -T, -O, etc) just like any other PCP command line tool. In the pmie language, the "units" are reserved keywords "sec" or "second" or "secs" or "seconds" ... I'm reluctant to add "s" to this list because of possible symbol clashes, e.g. an existing rule s = <my_favourite_expression>; would break (that's just the way the pmie lexical scanner works) and if I was persuaded that this was acceptable (which I'm not) it introduces a rat's nest of follow-ons, like "m" for "min", "h" for "hour", ... I'm inclined to suggest this be issue be closed as WONTFIX.
(In reply to Ken McDonell from comment #1) > Marko, in which context are you looking for "s" as an abbreviation? In the pmie language. But ... > It works on the command line (-t, -S, -T, -O, etc) just like any other PCP > command line tool. > > In the pmie language, the "units" are reserved keywords "sec" or "second" or > "secs" or "seconds" ... I'm reluctant to add "s" to this list because of > possible symbol clashes, e.g. an existing rule > > s = <my_favourite_expression>; > > would break (that's just the way the pmie lexical scanner works) and if I > was persuaded that this was acceptable (which I'm not) it introduces a rat's > nest of follow-ons, like "m" for "min", "h" for "hour", ... ... this is fair enough, I'll close this one. Thanks.