On Thu Jan 18 14:14:30 2007, mdiep wrote: > On Thu Jan 18 13:52:33 2007, leo wrote: > > While that was never actually specced, I do consider a NULL PMC as > > something > > like a null pointer in C. Any access (except testing for NULL-ness) > to > > it is > > an error. Above example tests, that some usage of a NULL PMC fails. > > > > It's of course debatable, which usage of NULL should be allowed, > e.g. > > above > > one. An explicit test in PMC->type conversion for PMCNULL in the MMD > > code is > > very likely all to make above code running (mmd.c:167,168). > > I based the bug report on the behavior of normal subs: > > .sub main :main > null $P0 > foo($P0) # this *does* print "foo\n" > .end > .sub foo > say "foo" > .end > > I don't know that I particularly need to be able to pass null PMCs to > a MultiSub, but I at least > demand a better error message. :-) I think either way will be trivial > to write, but it probably > needs some input from the architect. > > -- > Matt Diephouse >
The above code prints "Any" in the mmd branch. Unless that's an unwanted behavior, it looks like this ticket can be resolved once the mmd branch is merged.
