On 5 March 2014 19:12, Daniel H. Leidisch wrote:
> Jokes aside, while I'm all in favor of such extensions for tacit
> programming (composition, currying, hooks/forks/trains, as in NARS2000,
> NGN, newer versions of Dyalog, J), I think proper lambdas are a much
> more important and fundamental iss
Hi Juergen
> how does NARS2000 define f⍤B and A f⍤B (the standard does not)?
I can answer this.
f⍤y is just the function that would be applied to B in f⍤y B, so that one can
give it a name: g←f⍤y and then apply it: g B
A f⍤B is a syntax error, because f⍤B becomes a function, which then lacks th
Hi
I'd like to work on a beginner's documentation or tutorial on APL and GNU
APL in particular. The website mentions: "A Quick start document for APL is
planned but the work has not started yet.
Is there any existing work I'd have to coordinate with? Or can I start from
scratch?
Tobia
Hello
Is there a reason why GNU APL does not exit on EOF, aka. Ctrl-D on cooked
input? Every shell and interpreter I have ever used does so by default.
Maybe there are people who are used to typing "exit" or "logout" by hand,
but for those of us who have always hit Ctrl-D to exit from any interac
Thank you Jürgen.
I'm not sure values > 1 are working properly, but maybe that's just my
system. I've set it to 1 anyways.
As for the output messages, I suggest the attached changes, because 1)
readline is already ending CIN on Ctrl-D, so we don't need to output
another endl; 2) that "*** end of
ount > 0. I would leave the message as is because this
> is a
> rather unusual situation and the user should always be informed about it.
>
> /// Jürgen
>
>
> On 12/20/2014 01:13 PM, Tobia Conforto wrote:
>
> Thank you Jürgen.
>
> I'm not sure values >
/⍨ by itself seems to work:
(2|⍳3) / ⍳3
1 3
(⍳3) /⍨ 2|⍳3
1 3
But inside a lambda I get a syntax error:
{(2|⍵) / ⍵} ⍳3
1 3
{⍵ /⍨ 2|⍵} ⍳3
SYNTAX ERROR
λ1[1] λ←⍵/⍨2∣⍵
^ ^
Tobia
Hello
Sorry for opening a new post above, I did not realize this was already
being discussed here.
I'm far from being an APL expert, but I humbly believe the current behavior
to be a bug. Consider this expression, where A and B are arrays (or
scalars):
A F / B
If F is a function, then / s
the ISO standard nor the APL2 manual provide enough information to
> cleanly resolve these border cases.
> I have tried the "/ is always operator" approach earlier but it was
> breaking quite a few GNU APL testcases
> so I decided not to follow it.
>
> /// Jürgen
>
>
Hi Jürgen,
here's a little fix. The base64 chars had S and T misplaced.
Tobia
--- src/QuadFunction.cc(revision 520)
+++ src/QuadFunction.cc(working copy)
@@ -413,8 +413,8 @@
const ShapeItem full_quantums = B.element_count() / 3;
const ShapeItem len_Z = 4 *
Hello
It semes the parser does not like it when I juxtapose two lambdas:
{⍵} ⊢ {⍵} 3
3
{⍵} {⍵} 3
SYNTAX ERROR
{⍵}λ1 3
^ ^
Is this related to function / operator parsing?
Tobia
11 matches
Mail list logo
