Your suspicion is correct: I get an index error with debug turned off. Here's a partial stack trace
0 libj.dylib 0x0000000115ca1cde jtdebug + 110 1 libj.dylib 0x0000000115ca228d jtdbunquote + 253 2 libj.dylib 0x0000000115cd0951 jtunquote + 1153 3 libj.dylib 0x0000000115c47e4c jtfoldx + 188 4 libj.dylib 0x0000000115cc3417 jtparsea + 2807 5 libj.dylib 0x0000000115ca2172 jtparsex + 162 6 libj.dylib 0x0000000115c9cd93 jtxdefn + 6707 7 libj.dylib 0x0000000115c615b7 jtdfs2 + 39 8 libj.dylib 0x0000000115ca220f jtdbunquote + 127 9 libj.dylib 0x0000000115cd0951 jtunquote + 1153 ... Thanks, -- Raul On Tue, Jan 21, 2020 at 11:51 AM Henry Rich <[email protected]> wrote: > > I can't reproduce this on Windows. I get an index error, which is correct. > > Does the failure you see also occur if you remove the line > > 13!:0 (1) > > ? > > Henry Rich > > On 1/21/2020 10:51 AM, 'Sergey Kamenev' via Beta wrote: > > Hi! > > > > As far as I understand, this error should not occur even with the most > > erroneous code. > > > > J file and data file for him in attachment. > > > > Nice day! > > Sergey > > > > > > > > > > > > ---------------------------------------------------------------------- > > 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
