Forgot for a moment the main reason for {::: proposal.
Parsing rules allow for 1{::: as 2 separate tokens
They dont allow for 1Y. or (1i. for that matter)
On Monday, March 2, 2020, 06:15:08 p.m. EST, Raul Miller
<[email protected]> wrote:
X. and Y. require shift keys on my keyboard.
Meanwhile, as a general rule, if things have gotten to be complicated
enough that you need boxed arguments for a dyad, it's pushing things
to refer to the contents of those boxes numerically.
I mean, certainly, I've done that -- but I prefer other approaches.
(I should probably take my comments here to chat@ -- I'll do that next
time, I guess?)
Thanks,
--
Raul
On Mon, Mar 2, 2020 at 6:05 PM 'Pascal Jasmin' via Programming
<[email protected]> wrote:
>
> X. and Y. require no shift keys :)
>
> J is a language where functions that require more than 2 arguments, must pack
> these arguments into lists or boxes.
>
>
>
>
> On Monday, March 2, 2020, 03:22:12 p.m. EST, Raul Miller
> <[email protected]> wrote:
>
>
>
>
>
> X: and Y: would probably be more readable. And, sure, that would need
> a space in typical cases.
>
> That said, personally, I'm not particularly fond of working with boxed
> lists in tacit dyads.
>
> Thanks,
>
> --
> Raul
>
> On Mon, Mar 2, 2020 at 3:13 PM 'Pascal Jasmin' via Programming
> <[email protected]> wrote:
> >
> > consider the adverbs
> >
> > X =: (&({::))(@:[)
> >
> > Y =: (&({::))(@:])
> >
> > These are useful for extracting an item from either x or y parameter lists
> > (that may be boxed) tacitly
> >
> > 2 Y i.3 equivalent to (2 {:: ]) i.3
> >
> > shorter and doesn't require parentheses if not the right most part of a
> > fork.
> >
> > I'd propose {::: as a built in for Y, and {::. as built-in for X
> >
> > Though it is more typing to use compared to Y and X, it would allow for 0
> > spacing readability of adverbs/modifiers.
> >
> > You cannot type 2Y (as legal expression/name). You could type 2{:::
> >
> > Forks are more readable when all/as much as possible of the spaces separate
> > the tines.
>
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
