Re: Exporter::Safe by Eric Wilhelm- June 24, 2008 from David Cantrell on Tuesday 24 June 2008 06:40:>use Import; does Magick to make Exporter not work in anything called> from here>>use Module::That::Exports::Stuff; except that now it doesn&39;t,> bwahahahaha!>>Import::import(> from => &39;Module::That::Exports::Stuff&39;,> subs => qw(set get bet wet)>);That seems like a lot of typing. You can already get "import nothing" with..http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6654.html Re: Exporter::Safe by David Cantrell- June 24, 2008 On Fri, Jun 20, 2008 at 01:45:41PM +0100, Ovid wrote:> Buried deep within some code, someone used a module (Test::Most 0.03)> which exports a &39;set&39; function. They weren&39;t actually using that> module. It was just leftover cruft. Unfortunately, the parent class> of that module inherited from Class::Accessor.> > Test::Most exports &39;set&39; and Class::Accessor calls a &39;set&39; method. > Oops.> > I&39;m trying to think of the best way to deal with this. ..http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6653.html Re: Exporter::Safe by Fergal Daly- June 22, 2008 2008621 Ovid <publiustemp-moduleauthors2yahoo.com>:>> --- Hans Dieter Pearcey <hdp.perl.module-authorsweftsoar.net> wrote:>>> > never does anything to the importing package>> >>> > use Foo::Bar as => Bar;>> >>> > plops a constant function Bar into your package. The constant is an>> > object on which you can do>> >>> > Bar->some_function(args)>> >>> > and it is the equivalent of...http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6652.html Re: Exporter::Safe by Fergal Daly- June 21, 2008 2008620 Hans Dieter Pearcey <hdp.perl.module-authorsweftsoar.net>:> On Fri, Jun 20, 2008 at 04:19:41PM +0100, Fergal Daly wrote:>> To be a little more constructive. Here&39;s something that is>> implementable and I think reasonable.>>>> use Foo::Bar;>>>> never does anything to the importing package>>>> use Foo::Bar as => Bar;>>>> plops a constant function Bar into your package. The constant is an>> object on which you.http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6651.html Re: Exporter::Safe by Ovid- June 21, 2008 --- Hans Dieter Pearcey <hdp.perl.module-authorsweftsoar.net> wrote:> > never does anything to the importing package> > > > use Foo::Bar as => Bar;> > > > plops a constant function Bar into your package. The constant is an> > object on which you can do> > > > Bar->some_function(args)> > > > and it is the equivalent of calling> > > > Foo::Bar::some_function(args)> > In my TODO is an entry for implementing...http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6650.html Re: Exporter::Safe by Hans Dieter Pearcey- June 20, 2008 On Fri, Jun 20, 2008 at 04:19:41PM +0100, Fergal Daly wrote:> To be a little more constructive. Here&39;s something that is> implementable and I think reasonable.> > use Foo::Bar;> > never does anything to the importing package> > use Foo::Bar as => Bar;> > plops a constant function Bar into your package. The constant is an> object on which you can do> > Bar->some_function(args)> > and it is the equivalent of calling> >...http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6649.html Re: Must exist, right by David Nicol- June 20, 2008 this presumes a hash-based object instead of a field of a hash-basedobject, but it can have blessed members unlike Chris Dolan&39;s draft; italso takes multiple args to be slice keys rather than consecutiveaccesses into a deep AoA. Wrapping in an import function and theniftiness with closing over $fieldname has been left out,UNTESTED.package autoaccessor::ReadOnly;sub new shift; lose package name bless shift return what we were given, it had better be a hashrefsub AUTOLOAD ..http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6648.html Re: Must exist, right by Jonathan Rockway- June 20, 2008 On Thu, Jun 19 2008, Eric Wilhelm wrote:>>I think Moose is overkill for this type of thing but Andy++ for this>> thread, I&39;ve been looking for something like this for a while too :)>It&39;s overkill, but not for the reasons you mention. Moose is a classbuilder and meta object protocol. The Data::Auto::Objectify::Thing hasnothing to do with OO, really. It just wants to use OO syntax tomanipulate a data structure. There are definitely no classes involved,so using Moose...http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6647.html Re: Exporter::Safe by Eric Wilhelm- June 20, 2008 from Ovid on Friday 20 June 2008 05:45:>Test::Most exports &39;set&39; and Class::Accessor calls a &39;set&39; method.>Oops.>>I&39;m trying to think of the best way to deal with this. My first>thought is to create a drop in replacement for Exporter which will not>export a function if caller->can($function) unless the person>explicitly lists it in the import list with a unary plus:Even if you could detect yet-to-be-defined subs, that wouldn&39;t actually fix this...http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6646.html Re: Exporter::Safe by Fergal Daly- June 20, 2008 2008620 Ovid <publiustemp-moduleauthors2yahoo.com>:> Buried deep within some code, someone used a module (Test::Most 0.03)> which exports a &39;set&39; function. They weren&39;t actually using that> module. It was just leftover cruft. Unfortunately, the parent class> of that module inherited from Class::Accessor.>> Test::Most exports &39;set&39; and Class::Accessor calls a &39;set&39; method.> Oops.>> I&39;m trying to think of the best way to deal with this. .http://www.nntp.perl.org/group/perl.module-authors/2008/06/msg6645.html |