On Mon, 4 Mar 2013 10:04:42 +0100 Alexis Sukrieh <[email protected]> wrote: > 2013/3/4 Punter <[email protected]>: > > Couldn't we make it so, that if you include the plugin in > > config.yml, then you get its keywords everywhere where we just "use > > Dancer"? > > > > Please? > > > > I don't like that, because you end up with altering the context of a > Perl package via a config file. > > I'm really not a big fan of that. To me, whatever pollutes the > namespace should come from the code, this way there is no hidden magic > behind the scene, preventing horrible bugs like "where the f** is > coming this goo_bar keyword in my namesapce? I don't even load > anything in that package!".
I agree - if code is using any functions/keywords, I expect them to have come directly from one of the modules that the code in question has use'd up top. It would also make pre-req scanning tools such as Dist::Zilla's AutoPrereq plugin miss them. _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
