aboutsummaryrefslogtreecommitdiff
path: root/commentary
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2021-11-06 12:13:03 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2021-11-06 12:13:03 -0400
commit401cf4a444fbdc7e085eafe04171f9e2bbdc671e (patch)
tree9ad98e7a36e9ed715ffeac0fc428b19d9c29c418 /commentary
parent25da94bac66884a74a0f02e961a7165c8293a277 (diff)
Link to Adám's style guide as the source of BQN's name role system
Diffstat (limited to 'commentary')
-rw-r--r--commentary/history.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/commentary/history.md b/commentary/history.md
index cec68e01..13cd2151 100644
--- a/commentary/history.md
+++ b/commentary/history.md
@@ -74,7 +74,7 @@ Nathan Rogers suggested that assertion should be made a primitive to elevate it
#### Context-free grammar
-In YAG meetings, I suggested adopting [APL\iv](https://aplwiki.com/wiki/APL%5Civ)'s convention that variable case must match variable type in order to achieve a context-free grammar. Adám, a proponent of case-insensitive names, pointed out that the case might indicate the type the programmer wanted to use instead of the value's type, creating cross roles.
+In YAG meetings, I suggested adopting [APL\iv](https://aplwiki.com/wiki/APL%5Civ)'s convention that variable case must match variable type in order to achieve a context-free grammar. Adám, a proponent of case-insensitive names, pointed out that the case might indicate the type the programmer wanted to use instead of the value's type, creating cross roles. Although I considered swapping subjects and functions, I ended up using exactly the conventions of his APL [style guide](https://abrudz.github.io/style/#nc).
#### Headers