Skip Menu |
 

This queue is for tickets about the BEGIN-Lift CPAN distribution.

Report information
The Basics
Id: 119854
Status: open
Priority: 0/
Queue: BEGIN-Lift

People
Owner: stevan.little [...] gmail.com
Requestors: ether [...] cpan.org
Cc:
AdminCc:

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



Subject: port back to Devel::BeginLift?
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-31790-1484348855-1935.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 304
Download (untitled) / with headers
text/plain 304b
Show quoted text
> SEE ALSO > > Devel::BeginLift > > This does a similar thing, but does it via "some slightly insane perlguts magic", while this module has much the same goals, it will (hopefully) accomplish it with less insanity.
When your code is settled, we can certainly port it back to the original namespace.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-31790-1484348855-1935.0-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31790-1484348855-1935.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-22927-1484391780-59.119854-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 502
Download (untitled) / with headers
text/plain 502b
On Fri Jan 13 18:07:35 2017, ETHER wrote: Show quoted text
> > SEE ALSO > > > > Devel::BeginLift > > > > This does a similar thing, but does it via "some slightly insane > > perlguts magic", while this module has much the same goals, it will > > (hopefully) accomplish it with less insanity.
> > When your code is settled, we can certainly port it back to the > original namespace.
I see no need to do that, the old module can remain for those who want it and this new module can happily co-exist with that. - Stevan
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-22927-1484391780-59.119854-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31790-1484348855-1935.0-0-0 [...] rt.cpan.org> <rt-4.0.18-22927-1484391780-59.119854-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-12151-1484422113-199.119854-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 618
Download (untitled) / with headers
text/plain 618b
On 2017-01-14 03:03:00, STEVAN wrote: Show quoted text
> On Fri Jan 13 18:07:35 2017, ETHER wrote:
> > > SEE ALSO > > > > > > Devel::BeginLift > > > > > > This does a similar thing, but does it via "some slightly insane > > > perlguts magic", while this module has much the same goals, it will > > > (hopefully) accomplish it with less insanity.
> > > > When your code is settled, we can certainly port it back to the > > original namespace.
> > I see no need to do that, the old module can remain for those who want > it and this new module can happily co-exist with that.
Why have two implementations and clutter up the namespaces?
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-12151-1484422113-199.119854-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31790-1484348855-1935.0-0-0 [...] rt.cpan.org> <rt-4.0.18-22927-1484391780-59.119854-0-0 [...] rt.cpan.org> <rt-4.0.18-12151-1484422113-199.119854-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-30126-1484482979-1014.119854-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1819
Download (untitled) / with headers
text/plain 1.7k
On Sat Jan 14 14:28:33 2017, ETHER wrote: Show quoted text
> On 2017-01-14 03:03:00, STEVAN wrote:
> > On Fri Jan 13 18:07:35 2017, ETHER wrote:
> > > > SEE ALSO > > > > > > > > Devel::BeginLift > > > > > > > > This does a similar thing, but does it via "some slightly insane > > > > perlguts magic", while this module has much the same goals, it will > > > > (hopefully) accomplish it with less insanity.
> > > > > > When your code is settled, we can certainly port it back to the > > > original namespace.
> > > > I see no need to do that, the old module can remain for those who want > > it and this new module can happily co-exist with that.
> > Why have two implementations and clutter up the namespaces?
But, ... clutter is what CPAN is all about ;) I am not against possibly merging the two, in some way, eventually. Right now I think it would be ill advised to depend upon Devel::BeginLift as it (and B::Hooks::OP::Check::EntersubForCV) are not looking very healthy on newer perls. http://matrix.cpantesters.org/?dist=B-Hooks-OP-Check-EntersubForCV+0.09 http://matrix.cpantesters.org/?dist=Devel-BeginLift+0.001003 While I could try and fix that, I am honestly not interested in that distraction at the moment. I would rather stick with my hackish version until such time as I have tuits to revisit this in more depth. Basically, this module is just a small part of a larger picture, until I finish painting this larger picture, I am fine with the state it is in. Make sense? Totally fine with this, just ... later. (NOTE: In the spirit of that, ticket has been re-opened and assigned to me) Of course patches are always welcome, I personally like my namespace better, though I am not sold entirely on my API, nor am I sold on the Devel::BeginLift, but meh, all that can be discussed. Thanks, - Stevan


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.