> I hadn't heard the "quiche eater" term before, but shouldn't your quiche
    > eaters be restricted to writing MFC apps in Super Turbo Visual Basic++
    > with self-debugging GUI where all new code is just combining templates
    > that Must Not be Questioned provided by the software gods from the great
    > temple in Redmond?
    >

    Nah, when the term "quiche eater" was common it was generally used by
    assembler programmers having a dig at C and PASCAL programmers.

When I first heard it, I think it was primarilly directed against all
those unix weenies writing shell scripts, by the C programmers.

It all depends on who you want to insult, and who you want to compliment :-)

Probably you can use the 80/20 rule.  Pick a dividing line so that only
20% of the people qualify as non quiche-eaters.  Or 10%  Or 1%.

Unfortunately, one finds very often that the people in the top 10% of
writing efficient code and understanding your favorite language are not
the same as the top 10% of people who understand the problem that the
program is supposed to solve...

>>     He didn't know the difference between & and &&

Bits?  What are bits?  I've about given up on criticizing code like:

        flags |= BIT_ONE;
        flags |= BIT_TWO;
Instead of:
        flags |= BIT_ONE|BIT_TWO;

I just hope our compiler is good enough to do the right thing...

BillW

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body