On 2005-07-04, Dan Horne <[EMAIL PROTECTED]> wrote:
>
> 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.There is a naming convention for this. It's documented in CGI::Application under the heading "Writing Plugins". (If you have a suggestion on how this could be clear, please send a patch. ) http://search.cpan.org/~markstos/CGI-Application-4.01/lib/CGI/Application.pm#Writing_Plug-ins It happens that the ::DBH plugin pre-dates the recommendation and chooses not to follow it. However, If you write a plugin that related to the letters 'DBH' and you follow the proposed naming convention, there won't be a collision, because the "DBH" name space is already taken, so you would choose something else. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark Stosberg Principal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . . --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
