[Bro-Dev] patterns and &&/|| vs. &/| operators

[Jon Siwek]

On Tue, Jun 19, 2018 at 1:21 PM Vern Paxson <vern at corelight.com> wrote:

> Proposal: as part of adding bitwise &/| operators for counts, I'll
> also implement &/| operators for patterns, and remove the current
> &&/|| functionality.

The meaning of "p1 & p2" would be "yields a pattern that matches both
p1 and p2" versus the meaning of "p1 && p2" currently being "yields a
pattern that matches a p1 followed by a p2" ?

I'd generally say that deprecating (emit a warning message pointing to
each usage) for a time period is a more cautious approach.

- Jon