Repository navigation
Change ;: dyad #39
Description
I would like to propose two changes for the ;: dyad.
- We should be able to represent next state and output code as a single number. Instead of 2 3 for state 2, output code 3, we should be able to use 2.3.
- We should be able to request trace columns without having to represent all of them.
My motivation in both cases is compactness and efficiency. Of course, we have other ways of reaching these results. We could, for example, re-implement ;: in J. However, ;: is useful because of its compactness and efficiency. The benefits would be visual, as well as mechanical (especially on 64 bit systems). I have attached a proposed update to the dictionary
File:Proposed-d332.htm. (file was missing from wiki - ed)
-- @rdm<2009-06-03T19:33:10Z)>
Activity
tangentstorm commentedon Sep 15, 2021
ew when j = _1 instead of raising error, should emit an empty box in output code 0, nothing in output code 1, (i, 0) in output codes 2 and 4.
Benefit would open up classes of FSMs where tag/bracket delimited data can be output as pre-open/inside/post-close(and pre-open next) such that all within-tag/bracket (inside) content is in boxes at odd numbered indexes.
-- Pascal Jasmin 01:07, 12 June 2017 (UTC)