Interpreter bug reports in 2007 listed in the order when they were submitted. Bugs in 2005, 2006, current; library bug reports.


sparse arrays boxable (causes errors)

As reported by DevonMcCormick in the "Sparse array accumulation work-around" thread in the Forums, it is possible to end-run around the < sparse nonce error to box sparse arrays:

   a =. $.&.> a:
   datatype a
boxed
   datatype > a
sparse boolean
   
   ] b =. $. L: 0 ;/ i. 4 4
+-----+-----+------+------+
|1 | 1|0 | 4|0 |  8|0 | 12|
|2 | 2|1 | 5|1 |  9|1 | 13|
|3 | 3|2 | 6|2 | 10|2 | 14|
|     |3 | 7|3 | 11|3 | 15|
+-----+-----+------+------+

Using this type of array can result in problems:

     ;b
scheck a rank
|system error

-- DanBron 2007-01-06 17:48:57


spurious errors from commuted raze-cut

As reported in the Forum's "four boxes" thread, the special code for raze-cut appears slightly broken: {{{ NB. All equivalent per Dictionary specification

5 6 7 8 9 10 11 12 13 14

|domain error: g | (i.5 5) g 1,:2

5 6 7 8 9 10 11 12 13 14

5 6 7 8 9 10 11 12 13 14

|domain error: j | (i.5 5) j 1,:2

5 6 7 8 9 10 11 12 13 14 }}}

-- DanBron 2007-02-08 19:39:33


b. obscures -∞ ranks

The phrase u b. 0 obscures information when one or more of u's ranks are __; the adverb replaces such ranks with _ :

   u"0 __ 1 b. 0
0 _ 1

   9"__ i. 3   NB.  Rank operates properly.
9 9 9

This behavior does not contradict the Dictionary, any more than if b. replaced (ranks of) 0 with _, so this "bug report" may be a "feature request".

While it is defensible to substitute _ for ranks which are relative (to the shapes of the arguments), a rank of __ is absolute: it is effectively 0. Only negative finite ranks are relative.

-- DanBron 2007-04-11 14:13:47

   +/@(]"__) b. 0
_ _ _
   +/@(]"0) b. 0
0 0 0

   +/@(]"__) 1 2 3 4 5
15
   +/@(]"0) 1 2 3 4 5
1 2 3 4 5

System/Interpreter/Bugs07 (last edited 2008-12-08 10:45:45 by )