So this syntax:
filter filterSource by [keeping | discarding] [[the] {lines | items | keys
| elements}] {matching [wildcard | regex] pattern filterPattern | where
filterExpression} [into targetContainer]Would allow a shortened version: filter X by matching pattern "regex" into Z Which would expand to: filter X by keeping the lines matching regex pattern "regex" into Z On Sun, Aug 5, 2018 at 4:48 PM, Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote: > > > > On 6 Aug 2018, at 7:07 am, Mark Waddingham via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > filter X by keeping the lines not matching pattern "regex" > > My point was this statement can be written as both: > > filter X by keeping the lines not matching pattern “regex" > > and > > filter X by discarding the lines matching pattern "regex" > > So it would perhaps be a good idea to only allow `matching` rather than > `not matching` > > > Anyway - extending the current form with 'where' (rather than 'with > expression') is more than adequate at the moment. > > Hehe.. the `with expression` thing was me trying to come up with something > that worked with `with | without | matching | not matching`… `where` is > much better I agree. > > Cheers > > Monte > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
