|
|
|
| Do you know where your variables are? | |
| PerlMonks |
Re^8: Building Win32::GuiTest for perl 5.14 or higher (Bad tests!)by BrowserUk (Patriarch) |
| on Jun 25, 2012 at 21:18 UTC ( [id://978284]=note: print w/replies, xml ) | Need Help?? |
|
First, ... All of that would be equally applicable if the software translated failures of Win32::* modules from non-windows platforms into NA. Second, , ... And so does that. Indeed, you are just repeating my reasoning. The only difference between us here is that an author should not have to read a third party add-on's "authors guide" to disarm that third party add-on from scurrilously giving perfectly good modules and authors a bad reputation because the authors of that third party add-on are too damn lazy to fix their software. It would be the work of minutes for the authors of this crap to fix the problem -- which was pointed out to them years ago. It would take very little effort on their behalf -- ONCE -- to convert failure reports from non-windows testers for Windows-only modules into "Not applicable". Forcing -- ALL -- the authors of -- ALL -- those modules to have to mess with their preferences and requirements for their modules in order to disarm the misrepresentation of their code by mechanism they didn't ask for and cannot opt out of is just plain wrong! With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||||