Sounds drastic. How about inline comments?
On Fri, 27 Jan 2023, David Lambert wrote:
Intent: aid programmer to match parentheses in j sentences.
Problem: counting parens is insufficient, it's important also to enclose
the correct train grouping which can be difficult to see.
Solution: proposal uses named parenthesis to assist writing/reading j.
named paren are (id. and )id. identifier. must be that that would
trigger spelling error.
Implementation: interpreter ignores the identifier. Don't bother
matching open with close identifiers. The id becomes an in-line
comment. The word following ( or ) obeys identifier rules and also must
not interfere with (future) feature namespace, that is (a. interpreted
as it would be now ( a. . A paren followed without space by a spelling
error converts to that paren.
Example: (hook. (fork. u v w)f1. t)h1. becomes ((u v w) t) a fairly
common pattern for me in a longer sentence.
Current solutions: write my own j interface (me), follow spacing
recommendations ( ( ) ) (H.Rich), write short simple expressions mom
can read (K&R?) and exemplified by the j documentation.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
