Actually, my parenthetical suggestion should have been for {>{ A
${;{'a bc',&<&;:'def ghij'
1 3 1 4 2 3 2 4
${>{'a bc',&<&;:'def ghij'
2 2 2 4
Thanks,
--
Raul
On Mon, Jul 23, 2018 at 7:13 PM Raul Miller wrote:
>
> What would a higher ranked catalogue do? How would this be useful?
>
> (T
How would that work?
Thanks,
—
Raul
On Monday, July 23, 2018, Don Guinn wrote:
> I'm not sure this is something to be investigated at this time. Because I
> suspect that changing it's rank would not a trivial thing. All I asked is
> why the rank was set to 1. It appears pretty useless to me. H
{ y takes a list of boxes as input. That's really all you need to think
about. If you gave it more axes, what would it do with them? Since it
runs the items of the opened y together, there's no easy generalization
to higher dimensions. Thus, there are two choices: make rank infinite
and dec
I'm not sure this is something to be investigated at this time. Because I
suspect that changing it's rank would not a trivial thing. All I asked is
why the rank was set to 1. It appears pretty useless to me. How useful
would it be if it's rank were infinite? Not much. Simply (<"1) before
passing to
Hold on thar! I didn't want { y to work differently, I just misread the
spec. I don't think the current definition has any such restrictions as
you say. Try it with boxes containing whatever type you like.
Henry Rich
On 7/23/2018 6:42 PM, Don Guinn wrote:
It seems like the problem is that
What would a higher ranked catalogue do? How would this be useful?
(That asked... I imagine I could contrive some examples of catalogue which
take advantage of its current behavior. For example: {{A where 2=L.A )
Thanks,
—
Raul
On Monday, July 23, 2018, Don Guinn wrote:
> It seems like the pr
It seems like the problem is that Catalogue manadic rank is one. I really
can't see much use in passing it a table or higher rank of boxes. So what
about changing its monadic rank to infinite? It seems to me that that would
open up interesting possibilities, including as Henry wanted it to work in
No. But no argument for doing so either. Thus, I will not complicate
the code with the special case.
Henry Rich
On 7/23/2018 9:39 AM, Raul Miller wrote:
Any reason to not make the L.0 case for { use the <“1 implementation?
Thanks,
—
Raul
On Sunday, July 22, 2018, Henry Rich wrote:
I'll
I did not know this shortcut. Thanks for pointing it out.
On Mac OS X, one does not need to press the control key.
Depending on how you have your System Preferences set
up, you may or may not need to press the Fn key.
Dan
> On 22 Jul 2018, at 16:20, chris burke wrote:
>
> For the definition o
Any reason to not make the L.0 case for { use the <“1 implementation?
Thanks,
—
Raul
On Sunday, July 22, 2018, Henry Rich wrote:
> I'll get the answer to this one right. <"r is heavily optimized. Don't
> try to replace it.
>
> Henry Rich
>
> On 7/22/2018 7:08 PM, Don Guinn wrote:
>
>> Yes. T
Sounds good.
On Sun, Jul 22, 2018, 5:46 PM Henry Rich wrote:
> I'll get the answer to this one right. <"r is heavily optimized. Don't
> try to replace it.
>
> Henry Rich
>
> On 7/22/2018 7:08 PM, Don Guinn wrote:
> > Yes. The documentation describes exactly what's happening. The rank 1 is
> >
I'll get the answer to this one right. <"r is heavily optimized. Don't
try to replace it.
Henry Rich
On 7/22/2018 7:08 PM, Don Guinn wrote:
Yes. The documentation describes exactly what's happening. The rank 1 is
the key making each number an item. In this case it is the equivalent to
(<"1)
oops.
Henry Rich
On 7/22/2018 6:42 PM, neit...@gaertner.de wrote:
Henry Rich wrote:
As I read Ye Dic, ({ i. 2 4) should give the same result as
({ <"1 i. 2 3).
I never thought I'd have to say this to *you* but:
note that Catalogue { has rank 1.
Hence there should not be any interaction betwe
Yes. The documentation describes exactly what's happening. The rank 1 is
the key making each number an item. In this case it is the equivalent to
(<"1) by itself. So, is it a good idea to use ({) in place of (<"1) when
wanting to box something rank 1? It's shorter and simpler to read. But what
abou
Henry Rich wrote:
> As I read Ye Dic, ({ i. 2 4) should give the same result as
> ({ <"1 i. 2 3).
I never thought I'd have to say this to *you* but:
note that Catalogue { has rank 1.
Hence there should not be any interaction between the colors in
{ 'black' ,: 'green'
nor in the low / high ve
> I stumbled onto this by accident, but I can't find it documented anywhere.
>
> {i.3 4 5
You obviously know what i. does.
For the definition of { , in Jqt put the cursor on it (immediately to the
left or right as long as the selection is not ambiguous), then press
Ctrl+F1 or Ctrl+Shift+F1 for th
As I read Ye Dic, ({ i. 2 4) should give the same result as
({ <"1 i. 2 3). Put it on the bug list.
Henry Rich
On 7/22/2018 4:55 PM, Devon McCormick wrote:
I think for catalog to do anything interesting, you need to provide it with
boxed arguments.
So,
{ i.3
+-+
|0 1 2|
+-+
But
I think for catalog to do anything interesting, you need to provide it with
boxed arguments.
So,
{ i.3
+-+
|0 1 2|
+-+
But
{ (i.3);i. 2
+---+---+
|0 0|0 1|
+---+---+
|1 0|1 1|
+---+---+
|2 0|2 1|
+---+---+
It's providing all combinations of the items in boxes but, if there is no
e
I stumbled onto this by accident, but I can't find it documented anywhere.
{i.3 4 5
┌──┬──┬──┬──┐
│0 1 2 3 4 │5 6 7 8 9 │10 11 12 13 14│15 16 17 18 19│
├──┼──┼──┼──┤
│20 21 22 23 24│25 26 27 28 29│3
19 matches
Mail list logo
