Thanks, I'm going to give D::D::S a try, as I think it'll do what I'm looking for. Since I'm testing a subroutine that returns a data-structure (that happens to contain code-refs), I really don't care about the return values of the code-refs because those are tested elsewhere (through testing the closure subroutines) I just want to make sure that the structures are identical.
Thanks much for the suggestions! Andrew On 5/31/06 4:48 AM, "demerphq" <[EMAIL PROTECTED]> wrote: > On 5/30/06, chromatic <[EMAIL PROTECTED]> wrote: >> On Tuesday 30 May 2006 12:08, Nicholas Perez wrote: >> >>> Why not compare signatures? Is that not feasible? >> >> Which signatures? Is it important that the code comes from the same place >> (check the CV properties) or that the code has bound to the same lexicals >> (PadWalker) or that the lexicals are in the same state (more PadWalker)? > > And as Schwern said, if you are going to do all that stuff you might > as well use DDS to do it, as its much easier, (which is hardly > surprising as the Padwalker closure code was specifically written for > DDS'es requirements) > > Cheers, > Yve ---- Andrew Gianni Administrative Computing Services Computing and Information Technology University at Buffalo 215 MFAC, Ellicott Complex Buffalo, NY 14261-0026 716.645.3587x7124
