From a717221a7dd2fb88ff9d5d07e221a83dc558b47d Mon Sep 17 00:00:00 2001 From: Marshall Lochbaum Date: Fri, 23 Jul 2021 22:49:20 -0400 Subject: Update list notation links --- docs/doc/context.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/doc/context.html') diff --git a/docs/doc/context.html b/docs/doc/context.html index 8c0ea92e..b08f70a0 100644 --- a/docs/doc/context.html +++ b/docs/doc/context.html @@ -59,7 +59,7 @@

The associations between spelling and syntactic role are considered part of BQN's token formation rules.

One rule for typing is also best considered to be a pre-parsing rule like the spelling system: the role of a brace construct {} with no header is determined by which special arguments it uses: it's a subject if there are none, but a 𝕨 or 𝕩 makes it at least a function, an 𝔽 makes it a 1- or 2-modifier, and a 𝔾 always makes it a 2-modifier.

BQN's grammar

-

A formal treatment is included in the spec. BQN's grammar—the ways syntactic roles interact—follows the original APL model (plus trains) closely, with allowances for new features like list notation. In order to keep BQN's syntax context-free, the syntactic role of any expression must be known from its contents, just like tokens.

+

A formal treatment is included in the spec. BQN's grammar—the ways syntactic roles interact—follows the original APL model (plus trains) closely, with allowances for new features like list notation. In order to keep BQN's syntax context-free, the syntactic role of any expression must be known from its contents, just like tokens.

Here is a table of the APL-derived modifier and function application rules:

-- cgit v1.2.3