Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the nextgen CPAN distribution.

Report information
The Basics
Id: 62002
Status: resolved
Priority: 0/
Queue: nextgen

People
Owner: Nobody in particular
Requestors: mschwern [...] cpan.org
Cc:
AdminCc:

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



Subject: Loading oose in -e doesn't seem worth the trouble.
$ perl -Ilib t/02_02_DashE_w_nextgen.t 1..2 Indirect call of method "{" on object "Moose" at t/02_02_DashE_w_nextgen.t line 6. # Looks like your test exited with 255 before it could output anything. This is presumably because of the Filter::Simple call adding "use oose; \n use nextgen;" to the top of the program. This doesn't make any sense. * You're not likely to be writing Moose classes in a one liner. * It violates the "Moose won't load in package main" rule. * It introduces all the fun instability of a source filter. * on top of a source filter * Since you can't declare a package, it defeats the point of oose. The only utility I see is so that people can have an empty "Class" ready to go. This is a narrow use case, but it effects all one liners using nextgen slowing them down and adding instability. All to save writing -Moose. If nextgen is intended as a general purpose "improved Perl" module, I would recommend dropping it.
Show quoted text
> If nextgen is intended as a general purpose "improved Perl" module, I > would recommend dropping it.
I've decide you're right. For the time being it is more practical to drop it. -- Evan Carroll System Lord of the Internets http://www.evancarroll.com