Thanks, Jürgen.
I'm comfortable with this resolution.
I noticed the same typos on p. 110 of the ISO spec. It didn't occur to
me, though, to substitute Z←(R) ≠ (R).
Best wishes,
David
On Fri, 2014-05-16 at 16:40 +0200, Juergen Sauermann wrote:
> Hi David,
>
> not sure if it contradicts.
>
>
Hi David,
not sure if it contradicts.
(1) First of all the ISO standard says this about *A f¨ B* and *f¨ B:*
*9.2.6 Each*
...
For both forms:
If B is not empty, Signal domain-error.
...
I believe this is a typo and they mean "if B is empty". Thus according
to the ISO standard +¨'' is undef
Thank you. Confirmed working with the original test cases.
Pushing a bit further, I believe that the following behavior may still
be contrary to the IBM spec in SVN 268:
+¨''
┌⊖┐
│0│
└─┘
Here we have a numeric function passed an empty character. Transforming
this via the identity given pre
Hi,
thanks, hopefully fixed in SVN 268. Also the debug printouts.
/// Jürgen
On 05/14/2014 07:01 PM, David B. Lamkins wrote:
I think Elias is correct.
>From the IBM manual, pg. 110 (check the source; I think I've transcribed
accurately, but make no guarantee):
-- begin
Empty Argument: If R
I think Elias is correct.
>From the IBM manual, pg. 110 (check the source; I think I've transcribed
accurately, but make no guarantee):
-- begin
Empty Argument: If R is empty, the function LO is not applied. Instead,
a related function called the fill function of LO is applied with
argument ↑R (t
I tested this, and I'm wondering if the return value should really be 0?
Wouldn't it make more sense to return ⍬?
Regards,
Elias
On 15 May 2014 00:02, Juergen Sauermann wrote:
> Hi David,
>
> thanks, fixed in SVN 266.
>
> /// Jürgen
>
>
>
> On 05/14/2014 01:56 AM, David B. Lamkins wrote:
>
>> S
Hi David,
thanks, fixed in SVN 266.
/// Jürgen
On 05/14/2014 01:56 AM, David B. Lamkins wrote:
SVN Revision: 264
{⍵}¨''
SEGMENTATION FAULT
-- Stack trace at main.cc:122
-
SVN Revision: 264
{⍵}¨''
SEGMENTATION FAULT
-- Stack trace at main.cc:122
0x7f97fe168d65 __libc_start_main
0x43557d main
0x52627d Workspace::immediat
