Sorry if I stepped on anyone's toes.

Not at all, I meant the "5 points off" bit as a joke :). I know a fair number of python programmers and I'd label about 60% of them 'zealots.' Mind you, I'd probably label about the same number of Perl programmers 'zealots.' Don't even get me started on Java programmers... ;-)

*chuckles* I'll try not to - I've had my own share of experience with Java zealots, although those who actually are Smalltalk zealots and just have to use Java at work even though they despise it deep in their hearts are even worse. ;)

Oh, and as far as having programmed in every language is concerned - I guess that's impossible.

Yeah, that was a trick. I really work for NIMH. Anyone who claimed they did know every single programming language has been committed (regardless of whether or not they were telling the truth ;).

You do? Interesting. :) Anyhow, I can see why these people end up with you (*especially* those were the claim is actually true). ;)

Anyhow, why do you think switch (or goto, for that matter) is a low-level language concept?

Mostly because I've found that using dispatch hashes eliminates the need for them. I'm sure there's still a couple good uses, but sometimes I wonder if when a feature is that abused it wouldn't be better just to eliminate it. Yes, it's catering to the lowest common denominator and It would probably annoy all those write-25000-lines-of-assembly-before-breakfast kind of programmers, but my sanity would greatly appreciate it :).

Mmmm, I can't recall any assembly that features a switch instruction right now, unless you want to count C in as assembly (which has been described as an optimizing macro assembler with automatic register allocation in the past *g*). Seriously, though, I think that switch isn't that bad really; not all uses of switch boil down to (admittedly horrible, yet strangely fascinating) things like Duff's device. Besides, the Camel says that the main reason for not including switch was simply that there were many alternatives, from labelled bareblocks to foreach loops and from cascaded ?: operators to hashes - nothing hints that the exclusion of a proper switch statement might have been made due to it being too abused (or too easily abusable).

But IMO, it's all TMTOWTDI anyway - and I encourage languages to give you enough rope to hang yourself with, since that also means you'll have enough rope to tie the most beautiful and elaborate knots.

Speaking of breakfast, gotta run. Have a nice day :)

Heh. Thanks, and the same to you! ^_^

--
mowgli

In reply to Re^5: There's a level in Hell reserved for ________ by mowgli
in thread There's a level in Hell reserved for ________ by dws

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.