Skip Menu |

This queue is for tickets about the Queue-Base CPAN distribution.

Report information
The Basics
Id: 69069
Status: rejected
Priority: 0/
Queue: Queue-Base

People
Owner: RUSSOZ [...] cpan.org
Requestors: RUSSOZ [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Create a method to deep-copy the elements of the queue
Subject: [rt.cpan.org #69069] Fwd: Queue::Base and a copy() method
Date: Sun, 24 Jul 2011 18:29:04 -0300
To: bug-Queue-Base [...] rt.cpan.org
From: Alexei Znamensky <russoz [...] gmail.com>
Show quoted text
---------- Forwarded message ---------- From: Alexei Znamensky <russoz@gmail.com> Date: 24 July 2011 18:22 Subject: Re: Queue::Base and a copy() method To: Ron Savage <ron@savage.net.au> Hi Ron On 24 June 2011 00:48, Ron Savage <ron@savage.net.au> wrote:
> Hi Alexei > > On Thu, 2011-06-23 at 23:39 -0300, Alexei Znamensky wrote:
> > Hi > > > > On 22 June 2011 22:16, Ron Savage <ron@savage.net.au> wrote: > > [...] > >
> > > > > > Maybe it would be better to call the new method shallow_copy()? > > >
> > > > Well, I still intend to create a 'deep' version at some point, so it is > > going to be quite clear from that. And I made sure I mentioned that in
> the
> > documentation. > > > > I'm leaning towards keeping it, but anyway, I will refrain from releasing
> a
> > new version just for that. And will keep that in mind until next version, > > whenever that be.
>
How you doing? I am having second thoughts here. It kinda feels like we are adding something that doesn't belong there. KISS[1] comes to mind: a "queue" class shouldn't have to know anything about objects copying/serialization/whichever method used for that. And, as anyone wanting to perform a deep_copy can do that externally on its own, and then run $queue_deep_copy->copy, then I am considering leaving Queue::Base without this functionality. Similarly, you or I could ask for the maintainer of any given class in CPAN to provide a deep_copy method. The varied classes there don't *have* to know how to do that. Nor does Queue::Base. Not to mention we would add another bunch of classes to the dependencies list of Queue::Base, for a marginal benefit. It's not making much sense to me, now that I ave stopped to think about it. What do you think of it? Cheers, -- Alexei "RUSSOZ" Znamensky | russoz EM gmail com | http://russoz.org GPG fingerprint = 42AB E78C B83A AE31 7D27 1CF3 C66F B5C7 71CA 9F3C http://www.flickr.com/photos/alexeiz | http://github.com/russoz "I don't know. Fly casual!" -- Han Solo -- Alexei "RUSSOZ" Znamensky | russoz EM gmail com | http://russoz.org GPG fingerprint = 42AB E78C B83A AE31 7D27 1CF3 C66F B5C7 71CA 9F3C http://www.flickr.com/photos/alexeiz | http://github.com/russoz "I don't know. Fly casual!" -- Han Solo
 Rejected as it doesn't seem to make much sense to add this functionality in such a simple class.