in reply to Re^2: RFC: Mojolicious::Lite and Moo: A Very Basic Application Layout
in thread RFC: Mojolicious::Lite and Moo: A Very Basic Application Layout
This looks like error my $params->{nose} = $c->param('nose');
B::Deparse 1.1401 (perl 5.16...) doesn't know what that is :) ($my $params{'nose'} = $c->param('nose'));
I guess $xml is a lexical method, isn't it?
gratuitous :)
tobyinkster's argument goes
Stop writing 'private' methods ●If a method is useful for end-users, then promote it to a public method. ●If a method exists in your namespace, then document it. ●Otherwise, use 'lexical methods' – coderefs.
My argument goes, if you want it as a seperate method, document it, use _private convention, its as old as perl and its open
otherwise put it in sub nose
8/10 times I see a _lexical_method its useful to subclasses
The same goes for my %classdataUsefulButInaccessibleDirectly 8/10 times it should be our %...
Its like insideout objects ... as soon as you need to subclass and do something the author didn't think , all these OOPy protections become hurdles
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: RFC: Mojolicious::Lite and Moo: A Very Basic Application Layout
by karlgoethebier (Abbot) on Aug 05, 2015 at 23:49 UTC | |
by Anonymous Monk on Aug 06, 2015 at 00:29 UTC |