> [EMAIL PROTECTED] - Wed Dec 29 18:22:10 2004]: > > > This code: > > new P0, .Undef > new P1, .Undef > eq P0, P1, L1 > print "not " > L1: print "ok\n" > end > > prints "not ok". Should it? If Parrot considers every Undef PMC to > be distinct, it's going to make tasks like comparing arrays with > large numbers of undefined elements much fiddlier than it should be. > > For instance, the fact that Undef != Undef means that this code: > > new P0, .ResizablePMCArray > set P0, 1 > clone P1, P0 > eq P0, P1, L1 > print "not " > L1: print "ok" > print "\n" > end > > prints "not ok". > > Simon > > >
Can we get a design descision as to wheather or not Undef == Undef will ever have any meaning so we can close out this bug? The current beahvior of ./parrot foo.pasm MMD function __is_equal not found for types (78, 78) current instr.: '(null)' pc 6 (foo.pasm:3) seems wrong to me any way you look at it. -J --
