Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Re: The Perl Crackpot Index

by Solo (Deacon)
on Jul 26, 2005 at 14:14 UTC ( #478205=note: print w/replies, xml ) Need Help??

in reply to The Perl Crackpot Index

What about

? --Solo

You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.

Replies are listed 'Best First'.
Re^2: The Perl Crackpot Index
by Anonymous Monk on Jul 26, 2005 at 15:18 UTC
    Medium points for claiming there is a Possible bug in Perl?

    That shouldn't cost points.

    For one thing, there are bugs in various perl releases for various platforms. I know, I've submitted bug reports, and had them fixed. Heck, just read some of the Changelogs, or join the developer lists. Perl is good, but it's never been perfect, and probably never will be.

    Especially, we as a community shouldn't give people any social disincentive to provide bug reports, even if they're false alarms. Usually, the false alarms are raise about obscure or counter-intutive elements of the design of perl; they're exactly what one would expect people to stumble over.

    I'd assign points for claims like this:

    1. High points for "Perl can't be made readable, by any means"
    2. Medium points for "Perl is only a scripting language, not a real language"
    3. High points for "Perl is inherently inferior to language <X>, for every form of programming scenario"
    4. Medium points for "Perl is not a typed language"
    5. Low points for "Perl is not object oriented"
    6. High points for quoting "There's More Than One Way To Do It" in defense of poorly written code
    7. High points for re-implementing, poorly, a basic perl feature that you didn't know was in the language, such as simulating arrays with an "eval $var$index" type construct
    8. Very high points for re-implementing, poorly, a basic language feature that you did know was in the language, but disliked, such as replacing recursion with home-made finite state machine, because recursion is "complicated", but managing a list of tasks is "easy". *cough* *former boss* *cough*

      Medium points for claiming there is a Possible bug in Perl?
      That shouldn't cost points.

      In the spirit of the original CI:

      Medium points for claiming there is a Possible bug in Perl (without a good test case)


        Indeed! I thought about that one just after I created the node. The spirit of the original Crackpot Index is all about refusing to beleive that you may be the one who is wrong and shifting the blame to anything else that might be nearby. This is also one of the Three Pillars of brian's Guide to Solving Any Perl Problem. :)

        brian d foy <>
      Err, I think number 4 should read more like...
      4. High points for even mentioning "types" and "perl" in the same sentence.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://478205]
[erix]: spies should use a type-writer, no power needed, no auditable
[erix]: if all else fails, eat the paper
[erix]: a few years ago there was suddenly the news that the Kremlin was using typewriters again. Heard nothing about it afterward
[erix]: (maybe that means it worked)
[oiskuu]: Yeah, it might work as long as there are no root exploits. ;-)

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (6)
As of 2017-06-23 20:19 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (555 votes). Check out past polls.