-----BEGIN PGP SIGNED MESSAGE-----
Moin,
On Sunday 26 June 2005 07:18, Collin Winter wrote:
> > > My initial quick-glance at B::Deparse's documentation mentions
> > > something about perl optimising certain constants away, which could
> > > well throw a spanner into the works. Storable uses B::Deparse when
> > > serialising coderefs, though, so I'm certain there's a way around
> > > this.
> >
> > That shouldn't matter because any oddities B::Deparse applies to one
> > code ref it will apply to the other. For equivalent code the
> > decompiled result should be the same.
>
> After tinkering with B::Deparse for a bit, I think this particular
> "oddity" may just be a result of poorly-written docs (or, more
> probably, poorly-read on my part). The module seems to do the right
> thing in all cases I could come up with (i.e., it only optimises out
> truly-useless constants), so it should be safe to use for this
> particular purpose. With this matter sorted, I've started on the code
> and requisite tests to make the new stuff work.
Just for clarification: this means that:
is_deeply( sub { 1 + 2; }, sub { 3; } );
should/will pass because the subs compile to the same code?
Best wishes,
Tels
- --
Signed on Sun Jun 26 10:24:45 2005 with key 0x93B84C15.
Visit my photo gallery at http://bloodgate.com/photos/
PGP key on http://bloodgate.com/tels.asc or per email.
"My name is Felicity Shagwell. Shagwell by name, shag very well by
reputation."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQr5ml3cLPEOTuEwVAQEW9Qf+LP8XYCHoyVBYO3G535U7u76UzljgJNRS
BTY9yD6KhnAkff8pdlNk7TQhzF1iCYOhJEIvFUDKW07d9ChhQJlWv4j61/YUucwb
1yR1egvDtRpzaHPA7fDT/KpPbUSt4hAUiq88C3ULOkadw8ZxTPpsS3HKp7E0MW12
fbzWEf/Jaf02oZXBRaj4jsqSLgeuLIix2b/HeTAEHhx5gSUauWrjb14y4ed5tVO5
Q4hpCSSBJNwwwANMzwAztjoZsRefMuawURsFNkJvVffqDQSZfmunRiOYa/vvlRPP
yTs3WT/AYpwsSe47t/4+ua2Cw+M4LzBIZYM0YAHTNTVTDOFF3Cf2+w==
=+6+Q
-----END PGP SIGNATURE-----
