OK, export works, but...what if, e.g., the app wants to use multiple attributes handler modules ? Or some other attribute module needs to use my module ? When I created another stub attributes handler module, and use'd both modules, and applied both sets of attributes, only the last handler got invoked, presumably since its version of MODIFY_XXX_ATTRIBUTES replaced by the 1st module's version ?
Wrt Attributes::Handler, while I agree that the attributes.pm POD is only useful if you already know how to use attributes, my reasons for not using Attribute::Handler (as noted in my OP) arose from the following error occuring when trying to use the attributes under "perl -d" (on AS 5.8.6 WinXP) :
test_count set to 2 Test 1 Can't use an undefined value as a symbol reference at C:/Perl/lib/Attr +ibute/Han lers.pm line 16. at C:/Perl/lib/Attribute/Handlers.pm line 16 Attribute::Handlers::findsym('main', 'SCALAR(0x1b6e5cc)') call +ed at C:/ erl/lib/Attribute/Handlers.pm line 180 Attribute::Handlers::_apply_handler_AH_('ARRAY(0x1c3475c)', 'C +HECK') ca led at C:/Perl/lib/Attribute/Handlers.pm line 146 Attribute::Handlers::__ANON__[C:/Perl/lib/Attribute/Handlers.p +m:165]('m in', 'SCALAR(0x1b6e5cc)', 'Sociable') called at C:/Perl/lib/attributes +.pm line 6 attributes::import('attributes', 'main', 'SCALAR(0x1b6e5cc)', +'Sociable ) called at t\02shared_attr.t line 52 Debugged program terminated. Use q to quit or R to restart, use O inhibit_exit to avoid stopping after program termination, h q, h R or h O to get additional info. DB<1>