I'll be happy to send some bugreports or patches to existing modules, but I can't send patch which magically convert module developed without reliability and security in mind into reliable and secure module - it's much ease to develop own modules instead! (And this is what I'm doing - you can download a lot of my modules for free from my site.)
Then I take back my commentary about bugpatching. Yet my core point remains -- if you have time to create modules, then either a) continue to help with bugpatching, b) put 'em on CPAN, so we can easily run and compare (and so others can test out your modules from the CPAN testing framework), and/or c) write actual documents to help us understand what you mean by reliable/secure coding.
Otherwise, we'll never know what the heck you're talking about, because all you've done is rant. And rants rarely get anything done, but we're all impressed with solid, well-documented code and coding ideas.
----Asim, known to some as Woodrow.
| [reply] |
