chromatic wrote:
> With Parrot's type system, where the writer of the code (me) doesn't know at 
> code writing time what the type of the incoming data structures or individual 
> data members might be, what's a concise and maintainable way to port 
> is_deeply() to PIR?

Try a :multi first; if unsuccessful, compare type, and if match,
serialize both sides using freeze_pmc (or some kind of Dumper), and
compare the strings?

Thanks,
Audrey

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to