I thought I had a case where 13!:19]1 cut back the stack. I have not been able to reproduce that effect.
Sorry about the noise. -- Raul On Thu, Apr 7, 2022 at 5:56 PM Henry Rich <henryhr...@gmail.com> wrote: > > Oh, I see what you mean. I was taking for granted that y was evaluated > properly and was passed into 13!:19 as an argument. If then y is > invalid, 13!:19 gives an error and performs no action. > > I didn't understand what Raul meant by 'detected too late' and made my > best guess. > > Henry Rich > > > > On 4/7/2022 5:51 PM, Hauke Rehr wrote: > > Yes, but this > > > > No, y is ignored, except when it produces an error. > > > > reads like y may produce an error /inside/ rather than before. > > As if y would not be evaluated (and maybe throw) outside. > > > > I’d expect that actually y isn’t ignored in that case > > but the call doesn’t occur at all because the error comes first. > > > > Am 07.04.22 um 23:44 schrieb Henry Rich: > >> ? > >> > >> 13!:19 ] 1 > >> > >> is just a domain error, on that line. No action is performed. > >> > >> Henry Rich > >> > >> On 4/7/2022 4:56 PM, Raul Miller wrote: > >>> Eh... > >>> > >>> if I understand correctly, you are telling me that currently the error > >>> is detected too late? > >>> > >> > >> > > > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
