From 7c060bf6524ce63e34fe27a594851c295bed1231 Mon Sep 17 00:00:00 2001 From: s-ol Date: Wed, 27 May 2020 13:09:15 +0200 Subject: =?UTF-8?q?rename=20base.match.val=20=E2=86=92=20base.match.sig?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/internals/extensions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/internals/extensions.md b/docs/internals/extensions.md index 29cc075..0140e15 100644 --- a/docs/internals/extensions.md +++ b/docs/internals/extensions.md @@ -79,14 +79,14 @@ and the `Scope` the evaluation happened in. Ops generally shouldn't use the scope, but might look up 'magic' dynamic symbols like `\*clock\*`. #### argument parsing -Arguments should be parsed using `base.match`. The two exports `base.match.val` +Arguments should be parsed using `base.match`. The two exports `base.match.sig` and `base.match.evt` are used to build complex patterns that can parse and validate the Op arguments into complex structures (see the module documentation for more information). - import val, evt from require 'alv.base' + import sig, evt from require 'alv.base' - pattern = evt.bang + val.str + val.num*3 + -evt! + pattern = evt.bang + sig.str + sig.num*3 + -evt! { trig, str, numbers, optional } = pattern\match inputs This example matches first an `EvtStream` of type `bang`, then a `SigStream` -- cgit v1.2.3