Yup, funnily enough J501 gets it right too: 0x1 0 It seems that only 602 has this problem. 0p1 and 0e1 also behave correctly under 602.
On Wed, 2010-09-29 at 09:31 +0000, neit...@gaertner.de wrote: > bob therriault wrote: > > 0x1 > >2.71828 > > 9!:14 '' > >j602/2008-03-03/16:45 > > Certainly looks like a bug to me. > > 9!:14'' > 4.05+GDS changes/Feb 16 2008/19:19:49 > 0x1 > 0 > > Martin > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
