> The basic format seems good. I'm not sure about using weak_ref, though
> -- what if an object or structure falls out of scope, yet there's still
> a key in the data registry? If another ref comes along whose fingerprint
> matches that key, does it end up getting replaced with undef ? (I'm kind
>
The basic format seems good. I'm not sure about using weak_ref, though
-- what if an object or structure falls out of scope, yet there's still
a key in the data registry? If another ref comes along whose fingerprint
matches that key, does it end up getting replaced with undef ? (I'm kind
of sleepy
Here's the repackaged Data-Juxtapose.
I added the use of Scalar::Util (if available) just in case.
http://www.wafu.ne.jp/~daisuke/Data-Juxtapose-0.01.tar.gz
Let me know if there are any problems. If I don't hear anything, I'll
probably upload it to CPAN tomorrow.
--d
Daisuke Maki wrote:
>I like this... but I'd like to generalize this juxtapose thing into a
>separate package and release it, if it's okay with you guys (especially
>Matt)?
>
>
That's fine with me. How about Data::Juxtapose ? You'd probably want to
design it so that you can plug in different fi
Matt, Dave,
I like this... but I'd like to generalize this juxtapose thing into a
separate package and release it, if it's okay with you guys (especially
Matt)?
Something as simple as this:
my $j = Juxtapose->new;
@data = $j->juxtapose(@data);
If ok, do you guys have any suggestions for
Hello,
I updated my 'redundant data structure' fix so that it works with the latest
code in the repository and have included it below.
This only works for the PP versions of the zone modules. It was more of a proof
of concept -- there's probably more efficient ways to approach the problem.
(for e
