On Thu, 30 Sep 2021, Hauke Rehr wrote:
On the fork page, vvv and nvv share a row, and that’s for a good reason.
FWIW I added the NVV entry to that page, and I added it to the same row as
VVV only because the latter said 'creates a fork' rather than explicitly
showing the resulting verb (([x] f y) g [x] h y). And I think that it is
only pedagogically sound to say 'creates a fork' because the entire rest
of the page is dedicated to describing forks.
The old dictionary page does explicitly derive the resulting verb.
(http://juggle.gaertner.de/ref/dictionary/dictf.htm)
I think there should be two tables: one concise (for reference) and one
detailed (for learning); the former should join rows in the manner you
describe, and the latter should split them up (including separating VVV
and NVV forks).
Thoughts?
AN adv uA N
I don't like this so much. In most cases, it will violate the (expected)
convention that (V A) -> V. It also feels otherwise inconsistent, though
I am unable to explain why.
uA & N feels better, but I still do not like it.
NVC conj N V uCv
I support this.
I’d like to generalize forks to include what may be called a krof,
a flipped fork
AVN krof: (N V~ uA)
CVN krof: (N V~ uCv)
or is this impossible because …VN <-> …(VN) always takes precedence?
This is inconsistent with the proposed VVN. If VVN is legal then it
should be that:
AVN -> uA V N
CVN -> uCv V N
(At the same time, I support any form which increases the number of forks
that can be expressed...)
Thinking about AC made me wonder:
don’t we need conjunction analogues to ~?
(one for reflexive, another for passive)
NARS2000 has third-order functions, which it calls hyperators:
http://wiki.nars2000.org/index.php?title=Hyperators
That way lies madness.
In some sense, tacit modifiers are ~hyperators (in the same way that a
fork is a ~modifier), but I repeat: that way lies madness.
Most likely, I’d want to add something like
NVA adv N V uA
Currently NVA -> N (VA), a la VVA -> V (VA). So I would not change it.
-E
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
