Re^2: OOP in CGI

It was not meant to be a working fragment, merely an example of what I was talking about. :) I usually use

use CGI qw(:standard);

for my CGI apps (all two of them that I've made so far). I'm not really familiar with what has been called "namespace polution" but I assume it refers to an abundance of crap all in the namespace that can lead to more memory usage, longer access times, more processor usage, etc.

Comment on Re^2: OOP in CGI Download Code

Replies are listed 'Best First'.
Re^3: OOP in CGI by davorg (Chancellor) on Jul 29, 2005 at 09:29 UTC
"Namespace pollution" is where you end up having more symbols in your symbol table than the ones that you put there yourself. It can make things a bit confusing and the chances of having two symbols with the same name is increased. For example, if you have both `use CGI ':standard'` and `use LWP::Simple` in your program (which is a pretty common thing to want to do) then both of these modules try to export a subroutine called "head" into your symbol table. This will potentially lead to the universe exploding. -- <http://www.dave.org.uk> "The first rule of Perl club is you do not talk about Perl club." -- Chip Salzenberg	[reply]

Replies are listed 'Best First'.

Re^3: OOP in CGI
by davorg (Chancellor) on Jul 29, 2005 at 09:29 UTC

"Namespace pollution" is where you end up having more symbols in your symbol table than the ones that you put there yourself. It can make things a bit confusing and the chances of having two symbols with the same name is increased. For example, if you have both use CGI ':standard' and use LWP::Simple in your program (which is a pretty common thing to want to do) then both of these modules try to export a subroutine called "head" into your symbol table. This will potentially lead to the universe exploding.

--
<http://www.dave.org.uk>

"The first rule of Perl club is you do not talk about Perl club."
-- Chip Salzenberg

[reply]