> Hey, > I just wanted to pass along a note that my m0 branch: > https://github.com/nbrown/parrot/tree/m0-c-double-deref is currently > passing all m0 tests in the repository using my double deref approach > discussed below. > > I'm going to continue working on cleaning up the code and getting > closer to the spec, but I thought other people might like to see it. > -Nate
I'm not a expert, so I may be wrong. Here is my thought: 1. If double deref must be used here, then we should modify M0 spec to avoid it. 2. I don't like type conversion(casting) everywhere either, I think we can avoid it through the other way too. And we really need more eyes and more love on M0 spec and M0 implementation. Regards, Jimmy Zhuo
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
