Re^2: Responsibilities of a module author

in reply to Re: Responsibilities of a module author
in thread Responsibilities of a module author

~~Umm, define "core".~~ The perldoc to Switch states "There are undoubtedly serious bugs lurking somewhere in code this funky" and then goes on at some lengths about the limitations of source filters. TheDamian (the original author) categorizes Switch as a module "...you shouldn't use in production...", because it's an experiment. Given that, it'd take some pretty serious convincing for me to use the module for anything serious(especially since the functionality it implements is otherwise available).

Update: itub defined "core" for me, thanks :-). I missed it because Switch.pm isn't listed at the perl.5.8.7 page at search.cpan.org, though the download does contain it. Curious indeed.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

Comment on Re^2: Responsibilities of a module author
Re^3: Responsibilities of a module author by itub (Priest) on Nov 24, 2005 at 14:20 UTC
It is "core" because it comes with the perl distribution. People tend to (sometimes mistakedly, I have found!) trust those modules as more stable and reliable than the modules that are only found on CPAN. Why is it in the core if shouldn't be used in production? I don't know, but my guess is that it was a response to all the people who complain that Perl doesn't have a switch statement.	[reply]
Re^4: Responsibilities of a module author by Anonymous Monk on Nov 26, 2005 at 12:20 UTC
Its a mistake that Switch is in core, but once in core, always in core.	[reply]


more useful options
	PerlMonks

Re^2: Responsibilities of a module author

The best material for plates (tableware) is: