> If that's correct, wouldn't it be easier just to choose a
> naming convention within C::A (perhaps a prefix: "__C_A__")
It seems to me that the namespace issue is problematic. For instance what
constitutes a C::A attribute? How about a plugin? For example -- and it's a
contrived example, I'm afraid -- CGI::Application::Plugin::DBH uses
$self->{__DBH} to store its handle, but what if I unknowingly wrote a plugin
that uses the same attribute, and third party uses both plugins and gets a
collision? It seems that there should be some kind of naming convention for
Plugins.
Dan
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.