On 1/25/22 2:31 AM, Rob van der Heij wrote:
This is why "very different" is sometimes
better than "somewhat similar"
True that, friend.
--
Jack Woehr # Zen is a finger pointing at the moon.
IBM Champion 2021# Some want to see the moon.
http://www.softwoehr.com # Some want
On Sun, 23 Jan 2022 at 23:10, Jack Woehr wrote:
> On 1/23/22 2:55 PM, Rob van der Heij wrote:
> > The
> > motivation of not having to learn something new is less convincing, I
> think.
>
> Universal axiom, eh, friend?!
>
What I tried to say is that once we translate something like "sed" to CMS
So what you're saying is that we need a 'lookup' stage for other
environments/platforms, presumably including all the other stages from
that "doctor's bag" of remedies and the record-oriented and multi-stream
capabilities which make it all work.
Sounds good!
-- R; <><
On 1/23/22 13:20, Dave Jon
On 1/23/22 2:55 PM, Rob van der Heij wrote:
The
motivation of not having to learn something new is less convincing, I think.
Universal axiom, eh, friend?!
--
Jack Woehr # Zen is a finger pointing at the moon.
IBM Champion 2021# Some want to see the moon.
http://www.soft
On Sun, 23 Jan 2022 at 17:27, Jack Woehr wrote:
> Well, what I was idly wondering was whether the features exposed in CMS
> Pipelines can return the parenthesized groups in a regex.
>
No, the GREP we're talking about just selects records that match the
regular expression. When I did the PCRE for
Sir Rob has seen through my subterfuge to get the PIPSYSF and the grep
stages into the conversation; well played, Sir! :-) And he is of course
correct that a grep approach is not appropriate for solving this
problem. I much prefer his LOOKUP ideas.
While I have had positive results in my (very li
Well, what I was idly wondering was whether the features exposed in CMS
Pipelines can return the parenthesized groups in a regex.
On 1/23/22 8:57 AM, Paul Gilmartin wrote:
On Jan 23, 2022, at 08:04:36, John P. Hartmann wrote:
Select the range you wish to test | grep and you have the matching s
Select the range you wish to test | grep and you have the matching string.
However, I have never tested grep for interoperability with POSIX grep.
On 1/23/22 16:00, Jack Woehr wrote:
On 1/23/22 2:52 AM, Rob van der Heij wrote:
PIPSYSF in the main pipeline, but I don't think grep c.s. are the w
On 1/23/22 2:52 AM, Rob van der Heij wrote:
PIPSYSF in the main pipeline, but I don't think grep c.s. are the way
here.
grep itself is not what is wanted.
grep is an application built on regex.
me forget ... does pipelines have a regex stage to return groups from a
regular expression?
--
Jac
There's value in having common expressions across platforms and
environments. Witness the 'ifconfig' command Alan and company created years
ago for VM TCP/IP. (Later regretting that it lacked '-a'.)
Often the common component is only a portion, but combining segments is
trivial. Think outside the
Diverting the thread ...
On Fri, 21 Jan 2022 at 16:14, Dave Jones wrote:
> Hi, Peter.
> When I see a task like your's "need to check this message for either of
> the strings below", I think about using grep. Several versions of grep
> (egrep, fgrep, and ggrep) are supported by CMS Pipelines in t
11 matches
Mail list logo
