• (cs) in reply to ehabkost
    ehabkost:
    Gene Wirchenko:
    Manni:
    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?


    You first.  Use your classification system, the one that seems to be missing anything not critical of others.


    I think I will be rich if I start selling Sarcasm Detectors here. Anybody wants to join me on this business?


    Do your sarcasm detectors work?  Some so-called sarcastic remarks are actually straight responses, and vice versa.  It is hard to tell when facial expressions, tone of voice, pauses in voices, and other factors are not available.  If you think you have it down totally, you are probably fooling yourself.  I gave up on being 100% sure a long time ago.

    Sincerely,

    Gene Wirchenko

  • (cs) in reply to Gene Wirchenko

    Gene Wirchenko:

    Do your sarcasm detectors work?  Some so-called sarcastic remarks are actually straight responses, and vice versa.

    What a great observation.  I mean it.  Really.

    With the most wamest of regards, not sarcastically,

    Me.

  • (cs) in reply to Meddler
    Meddler:
    Mung Kee:
    Meddler:
    They'd at least be tolerable if they were pure acronyms (pronouncable) and not just initialisms.  Like, uh, RELOBLOPOCOCO.  That's much more fun to say!


    Oh, you mean pronouncable like "SQL?"


    Some still insist on saying each letter instead of using the established pronouncable acronym we all love.  It's interesting how one pronunciation becomes preferable to another. We could be going around saying "I love how easy it is to install my squall in windows."   And sometimes the word doesn't quite fit - around here people say NMEA (a type of GPS signal) as "nee-ma" as if it's NEMA.


    We had a pow-wow regarding pronunciation of acronyms a couple weeks ago, which is why I posted that.
  • (cs) in reply to ehabkost
    ehabkost:
    Gene Wirchenko:
    Manni:
    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?


    You first.  Use your classification system, the one that seems to be missing anything not critical of others.



    I think I will be rich if I start selling Sarcasm Detectors here. Anybody wants to join me on this business?

    Actually, I'm not sure where sarcasm comes in here.  However, some people could use a de-hyper-sensitzer around here.  I thought just hanging around here would work but apparently not.

  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:

    Do your sarcasm detectors work?



    I would be rich because there is a big demand for them, here. Not that I know exactly how to make perfect detectors.

    But that was funny when you asked for his classification, when the (F) option was specially designed for him. :)

  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:
    You first.  Use your classification system, the one that seems to be missing anything not critical of others.

    Sincerely,

    Gene Wirchenko

    <FONT face="Courier New" size=2>parse error: line 1</FONT>

    <FONT face="Courier New" size=2>sincerely,</FONT>

    <FONT face="Courier New" size=2>the compiler</FONT>

  • (cs) in reply to Manni

    Manni:
    Which type of post-whore are you?

    <FONT face="Courier New" size=2>i am the defender of the faith.  bring me cabbage as sacrifice.</FONT>

  • (cs)

    Well it has to be that way.  After all, you never know when you might want to change the letZero fuction from using the value of 'z' to 'Z'.    And that is just one of the letFOO fuctions, what if the value of  backslash changes?   What if you want to do more action in your let fuction  letSpace might look like this you know:




    bool g_fFunkySpaceHandleing = FALSE;   /* mispeslling
    intentional to avoid name conflicts with the other funkySpace global
    variable */


    letSpace(lcrBuffer, lmpAction) {
      if(isTrue(g_fFunkySpaceHandleing) {
        ...
      }
      else {
        ...
      }
    }

    See how much easier it was to make this change?  Brillant

  • pete (unregistered)

    I hear there is a job opening at the local McDonalds where this guy lives... He either escaped there, or should definately go there to apply....

  • (cs) in reply to Manni
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.



    Uh, whats this sex thing you speak of? 

    You forgot one:

    H) The Justifier: They find enjoy finding some excuse why the code must be done this way, and the code the the Optimizer came up with is wrong.   The idea that most of us do not deal with such thing as 3+ state bits, processors with a list of instrucitons that work, and other relics of the cold war KGB's attempts to confuse the CIA are not of interst to these people.  These people are the best part of the daily WTF and should be encoueraged.  (you can guess which one I am today)
  • Anonymous Coward's nephew (unregistered)

    I think I'll have to get some tonight to get over that.

  • (cs) in reply to hank miller
    hank miller:
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.



    Uh, whats this sex thing you speak of? 

    You forgot one:

    H) The Justifier: They find enjoy finding some excuse why the code must be done this way, and the code the the Optimizer came up with is wrong.   The idea that most of us do not deal with such thing as 3+ state bits, processors with a list of instrucitons that work, and other relics of the cold war KGB's attempts to confuse the CIA are not of interst to these people.  These people are the best part of the daily WTF and should be encoueraged.  (you can guess which one I am today)

    Y'know what I think is great? That someone posted their suggestion for a "G" entry to the list, and Hank Miller was smart enough to suggest this new option as "H". It's people like you that make this board fun to read.

    Sarcasmo-meter 3000 rating for this message: 0.0 - No sarcasm detected.

  • (cs) in reply to Manni
    Manni:
    Sarcasmo-meter 3000 rating for this message: 0.0 - No sarcasm detected.


    Bah!  Busted already.  Does this thing have a warranty?  Ah, throw it in the closet with the rest of them.

    Sincerely,

    Gene Wirchenko

  • Todd Aspeotis (unregistered) in reply to Dave

    What. The. Fuck.

    How can you be so stupid? Like really. This just defies stupidity. Did he write a tool in some other langauge to do those Let*Equal, because it would be ironic if he had something like

    printf("Let%sEqual (...)\n{\tlcrCurrent += %d", szCharName, cChar);

    Somewhere in it.

  • toxik (unregistered) in reply to Manni
    Manni:
    hank miller:
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.



    Uh, whats this sex thing you speak of? 

    You forgot one:

    H) The Justifier: They find enjoy finding some excuse why the code must be done this way, and the code the the Optimizer came up with is wrong.   The idea that most of us do not deal with such thing as 3+ state bits, processors with a list of instrucitons that work, and other relics of the cold war KGB's attempts to confuse the CIA are not of interst to these people.  These people are the best part of the daily WTF and should be encoueraged.  (you can guess which one I am today)

    Y'know what I think is great? That someone posted their suggestion for a "G" entry to the list, and Hank Miller was smart enough to suggest this new option as "H". It's people like you that make this board fun to read.

    Sarcasmo-meter 3000 rating for this message: 0.0 - No sarcasm detected.


    To be honest, I noticed that too - and .. I did read through the comments >:)

    I can't really class myself as anyone of those, I just read the code and reply what I thought after reading the comments (and do you guys have to post so much worthless shit that you have to scroll by? >:\ )
  • (cs) in reply to Manni
    Manni:
    hank miller:
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.



    Uh, whats this sex thing you speak of? 

    You forgot one:

    H) The Justifier: They find enjoy finding some excuse why the code must be done this way, and the code the the Optimizer came up with is wrong.   The idea that most of us do not deal with such thing as 3+ state bits, processors with a list of instrucitons that work, and other relics of the cold war KGB's attempts to confuse the CIA are not of interst to these people.  These people are the best part of the daily WTF and should be encoueraged.  (you can guess which one I am today)

    Y'know what I think is great? That someone posted their suggestion for a "G" entry to the list, and Hank Miller was smart enough to suggest this new option as "H". It's people like you that make this board fun to read.

    Sarcasmo-meter 3000 rating for this message: 0.0 - No sarcasm detected.



    I had a couple of suggestions as well.  And just so I can make this board fun for you:

    I)  Illiterate Literate:  These posters appear to be illiterate and will post comments that have already been made.  Usually posting anonymously, they appear to be trying to show their intellect while instead showing themselves to be completely retarded.

    J) Never-Happy:  These posters will  keep adding on to lists made by a poster in their ever-continuing attempts to improve it.  They are generally pathetic, shallow individuals who believe that other people care what they think.
  • (cs) in reply to toxik

    How about:

    K) Master of the Tangential. This person does little except complain about the forum software ("The real WTF is this forum...") and how they can't get a slice of pizza to display.

  • (cs) in reply to John Smallberries

    The real WTF is why the slice of pizza isn't on my plate.

  • Orinocohol (unregistered) in reply to Manni
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    A) Catch-phraseologist: They take portions of previous posts and make inside joke references to them. The most frequently-seen of these are "brillant" and "IsTrue( )". Newcomers to the site are confused and try to correct these apparent errors, while the seasoned veteran readers don't find it at all amusing. Continued pathetic attempts at humor like this will be met with a stapler to the face.

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.

    C) The one-liner: It's as simple as that, they post one line that gives no further insight or comedic value to what everyone else reads. It could be as simple as "W... T.... F!?!" Thank you for the affirmation that we are, in fact, viewing The Daily WTF. There was no point to your post, my life would have been better without it because I wouldn't have wasted 2 seconds reading your trite submission. Quite a few of these people are "Anonymous" posters because they are afraid that registering an account with their email address will cause satellites to beam communist thoughts into their brain via microwaves.

    D) The optimizer: These geniuses quickly identify that the post of the day has logic flaws, spelling errors, or over-complex methods of performing simple tasks. As a way of showing off their programming skills, they re-write the post of the day to be the fastest and most stable piece of code known to man. If you printed their code out, you could take it to a bank becuase it's made of gold. Figure it out bonehead, the code was posted because it sucks. No one cares if you can write it better. It's especially fun when they "optimize" it in a different programming language, which makes the whole concept even less useful.

    E) The "first" post: They like to be at the top of the list, with the fame and notoriety of having the very first response to every article. These people are also one-liners, because they never have anything else to say except "First!" These people are tard-monkeys, useless members of society who will most likely grow up to be politicians. 'Nuff said.

    F) The whiner: They rarely have anything to contribute to the topic. Instead they complain about how people's conversations are going off on a huge tangent, and they try to find new and creative ways to insult those people like calling them names in different languages, or coming up with overly-descriptive lists of the types of people that piss them off. These people should be shot.


    I'm amazed. Your post actually counts as meta-humour since, with a little stretching of the definitions, your own post fits happily into category F). Not that I don't completely agree with you, but still, sweet.
  • Dan F (unregistered) in reply to Gene Wirchenko

    Although that is a possibility, each function is slightly different. There is some code in each procedure which double checks to make sure it is the right character.

    The rest of the code is also full of priceless gems.

    Be glad you don't have to re-write it

  • (cs)

    I woulda liked to see one of the LetFoo functions, because as is, I don't even have a clue what this function is supposed to do.

  • (cs) in reply to Gene Wirchenko

    Gene Wirchenko:
    Please do not strain for acronyms.  It is undignified.  (See the rest of the IT industry for copious examples.)

    Note that my attempts at such acronyms are satire. I much loath the absurdity of IT buzzword/acronyms. AJAX is one of the most painful examples of these. If killing its creator would undo the word, I swear, I would do it ten times over.

  • Dan F (unregistered) in reply to seebs 
    within most of the LetFoo functions(the ones for special characters are different)

    int i, j;
    char temp;
      i = 0;
      j = i;
      while (j == i)
        {
        if(lcrBuffer.CurrentChar == 'Foo'){
    	j = 1;
        }
        if(lcrBuffer.CurrentChar != 'Foo'){
    	lcrBuffer.CurrentChar = getnextchar(lcrBuffer,lmpAction);
            j = i;
        } // 
      }
      if(j == 1){
       lcrbuffer.CurrentCharvalue = 123;
      
    }

    so it may not be 30 lines. I really wish I was making this stuff up
  • (cs) in reply to Manni
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    A) Catch-phraseologist: They take portions of previous posts and make inside joke references to them. The most frequently-seen of these are "brillant" and "IsTrue( )". Newcomers to the site are confused and try to correct these apparent errors, while the seasoned veteran readers don't find it at all amusing. Continued pathetic attempts at humor like this will be met with a stapler to the face.

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.

    C) The one-liner: It's as simple as that, they post one line that gives no further insight or comedic value to what everyone else reads. It could be as simple as "W... T.... F!?!" Thank you for the affirmation that we are, in fact, viewing The Daily WTF. There was no point to your post, my life would have been better without it because I wouldn't have wasted 2 seconds reading your trite submission. Quite a few of these people are "Anonymous" posters because they are afraid that registering an account with their email address will cause satellites to beam communist thoughts into their brain via microwaves.

    D) The optimizer: These geniuses quickly identify that the post of the day has logic flaws, spelling errors, or over-complex methods of performing simple tasks. As a way of showing off their programming skills, they re-write the post of the day to be the fastest and most stable piece of code known to man. If you printed their code out, you could take it to a bank becuase it's made of gold. Figure it out bonehead, the code was posted because it sucks. No one cares if you can write it better. It's especially fun when they "optimize" it in a different programming language, which makes the whole concept even less useful.

    E) The "first" post: They like to be at the top of the list, with the fame and notoriety of having the very first response to every article. These people are also one-liners, because they never have anything else to say except "First!" These people are tard-monkeys, useless members of society who will most likely grow up to be politicians. 'Nuff said.

    F) The whiner: They rarely have anything to contribute to the topic. Instead they complain about how people's conversations are going off on a huge tangent, and they try to find new and creative ways to insult those people like calling them names in different languages, or coming up with overly-descriptive lists of the types of people that piss them off. These people should be shot.

    This is pretty cool. Though the One Liners (C), can be annoying, I totally understand. It's an unavoidable reaction that simply *must* be communicated due to the extremeness of a condition. Kinda like the male's natural reflex to seeing the incredibly attractive, low-cut female: Daaaaammmnn!

  • (cs) in reply to Manni
    Manni:

    Which type of post-whore are you?

    no, wait, you are the Troll-type, since I need to check that option in order to see your post [H]

  • AKrotkov (unregistered) in reply to hank miller
    hank miller:
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.



    Uh, whats this sex thing you speak of? 

    You forgot one:

    H) The Justifier: They find enjoy finding some excuse why the code must be done this way, and the code the the Optimizer came up with is wrong.   The idea that most of us do not deal with such thing as 3+ state bits, processors with a list of instrucitons that work, and other relics of the cold war KGB's attempts to confuse the CIA are not of interst to these people.  These people are the best part of the daily WTF and should be encoueraged.  (you can guess which one I am today)


    That's the one I was thinking of, myself.

    And that code looks sort of like what an Excel macro would create. Except in C.
  • (cs) in reply to Manni
    Manni:

    Which type of post-whore are you?

    There are several basic types of people who post on this board. Can you tell which one you are?

    A) Catch-phraseologist: They take portions of previous posts and make inside joke references to them. The most frequently-seen of these are "brillant" and "IsTrue( )". Newcomers to the site are confused and try to correct these apparent errors, while the seasoned veteran readers don't find it at all amusing. Continued pathetic attempts at humor like this will be met with a stapler to the face.

    B) Uber-geek: These argumentative assholes will write up a dissertation-sized response in which they go into detail about processor architecture and kernel operations, even if the WTF has to do with Javascript. They ignore the true nature of the problem originally posted, and prefer to engage in pointless debates with other uber-geeks. To these people, sex involves a keyboard, and no physical contact.

    C) The one-liner: It's as simple as that, they post one line that gives no further insight or comedic value to what everyone else reads. It could be as simple as "W... T.... F!?!" Thank you for the affirmation that we are, in fact, viewing The Daily WTF. There was no point to your post, my life would have been better without it because I wouldn't have wasted 2 seconds reading your trite submission. Quite a few of these people are "Anonymous" posters because they are afraid that registering an account with their email address will cause satellites to beam communist thoughts into their brain via microwaves.

    D) The optimizer: These geniuses quickly identify that the post of the day has logic flaws, spelling errors, or over-complex methods of performing simple tasks. As a way of showing off their programming skills, they re-write the post of the day to be the fastest and most stable piece of code known to man. If you printed their code out, you could take it to a bank becuase it's made of gold. Figure it out bonehead, the code was posted because it sucks. No one cares if you can write it better. It's especially fun when they "optimize" it in a different programming language, which makes the whole concept even less useful.

    E) The "first" post: They like to be at the top of the list, with the fame and notoriety of having the very first response to every article. These people are also one-liners, because they never have anything else to say except "First!" These people are tard-monkeys, useless members of society who will most likely grow up to be politicians. 'Nuff said.

    F) The whiner: They rarely have anything to contribute to the topic. Instead they complain about how people's conversations are going off on a huge tangent, and they try to find new and creative ways to insult those people like calling them names in different languages, or coming up with overly-descriptive lists of the types of people that piss them off. These people should be shot.



    You know, this could actually be applied to all internet forums, not just dailywtf. It should be reworked to be more general, with specific amendments tailored for this site.

    <code>
    if (isTrue(you_dont_believe_me))
       ICanShowYouDocumentsAndWhitePapers( to_prove_my_point );
    else
        keepYourPostsOnTopic();
    </code>

    Frost Piss?
  • (cs) in reply to Manni

    Challenge: come up with the shortest possible post that meets ALL of the post-whore criteria A) through F)

  • Chris (unregistered) in reply to Meddler
    Meddler:
    Mung Kee:

    Oh, you mean pronouncable like "SQL?"


    Some still insist on saying each letter instead of using the established pronouncable acronym we all love.


    IIRC, MySQL insists on being pronounced "My Ess Cue Ell."

    Anyway, the OP makes me feel like a motherless child. Especially since each of the Let* functions probably contains an IsEqual function:

     if (arg1 == '@' && arg2 == '@')
      return TRUE;
     if (arg1 == '@' && arg2 == 'A')
      return FALSE;
     if (arg1 == '@' && arg2 == 'B')
      return FALSE;
    .
    .
    .

    --Chris
  • (cs) in reply to Dan F
    Anonymous:
    within most of the LetFoo functions(the ones for special characters are different)

    int i, j;
    char temp;
      i = 0;
      j = i;
      while (j == i)
        {
        if(lcrBuffer.CurrentChar == 'Foo'){
    	j = 1;
        }
        if(lcrBuffer.CurrentChar != 'Foo'){
    	lcrBuffer.CurrentChar = getnextchar(lcrBuffer,lmpAction);
            j = i;
        } // 
      }
      if(j == 1){
       lcrbuffer.CurrentCharvalue = 123;
      
    }

    so it may not be 30 lines. I really wish I was making this stuff up

    This is worthy of a WTF submission of its own. Somehow, he took the basic approach I had feared he took (see my post for 9:06pm yesterday), and increased the WTF density! Extra points for the sheer diversity of WTFs.

    I don't get the last line. Is 123 meant to represent the integer value of 'foo' which is assigned right back to the string element it came from? Are you telling us the whole heap of code does nothing?

    I think we are in the presence of a master.

    --RA

  • (cs) in reply to Chris
    Anonymous:
    Meddler:
    Mung Kee:

    Oh, you mean pronouncable like "SQL?"


    Some still insist on saying each letter instead of using the established pronouncable acronym we all love.


    IIRC, MySQL insists on being pronounced "My Ess Cue Ell."

    Anyway, the OP makes me feel like a motherless child. Especially since each of the Let* functions probably contains an IsEqual function:

     if (arg1 == '@' && arg2 == '@')
      return TRUE;
     if (arg1 == '@' && arg2 == 'A')
      return FALSE;
     if (arg1 == '@' && arg2 == 'B')
      return FALSE;
    .
    .
    .

    --Chris


    The good people who offer us MySQL tell us:

    " The official way to pronounce 'MySQL' is 'My Ess Que Ell' (not 'my sequel'), but we don't mind if you pronounce it as 'my sequel' or in some other localized way."

    Sounds to me like there is an official acknowledgement that "sequel" is, at least, and acceptable way to pronounce SQL -- if a product's producers are willing to allow an alternative pronunciation for a trademarked name in order to accomodate existing usage, it's probably a sign that the usage is pervasive.
  • (cs) in reply to Dan F
    Anonymous:
    within most of the LetFoo functions(the ones for special characters are different)

    int i, j;
    char temp;
      i = 0;
      j = i;
      while (j == i)
        {
        if(lcrBuffer.CurrentChar == 'Foo'){
    	j = 1;
        }
        if(lcrBuffer.CurrentChar != 'Foo'){
    	lcrBuffer.CurrentChar = getnextchar(lcrBuffer,lmpAction);
            j = i;
        } // 
      }
      if(j == 1){
       lcrbuffer.CurrentCharvalue = 123;
      
    }

    so it may not be 30 lines. I really wish I was making this stuff up

    This is craptacular.
    I've never seen such awful loop control.
    He's heard of  "if" but  not "else"?
    Doesn't this buffer object have character indexing?
    If he's dealing with chars, why have a CurChar and CurCharvalue elements?

    It just looks completely amateurish.
  • A. Noni Mouse (unregistered) in reply to Chris
    Anonymous:

     if (arg1 == '@' && arg2 == '@')
      return TRUE;
     if (arg1 == '@' && arg2 == 'A')
      return FALSE;
     if (arg1 == '@' && arg2 == 'B')
      return FALSE;
    .
    .
    .

    --Chris


    no no no, you've got it all wrong. with THAT code, the function would stop as soon as it passed one of those conditions. we can't have that!

    int x = 0;
    bool returnValue;
    if (arg1 == '@' && arg2 == '@')
      x = x + 1;
    if (arg1 == '@' && arg2 == 'A')
      x = x + 0;
    if (arg1 == '@' && arg2 == 'B')

      x = x + 0;
    ...
    if (x == 0)
      returnValue = false;
    if (x > 0)
      returnValue = true;
    return returnValue;


    you gotta let these compilers know who's boss.

  • (cs)

    Well...this is obvious. It's core level code for the next generation search engine.

  • zeroWS (unregistered) in reply to Totoro
    Anonymous:
    It has got to be computer made. While I am now fully convinced there are people out there stupid enough to do this, the chance of finding one with this amount of patience as well is next to none.


    He used to work for me. I can give you his name if you'd like.

    I am not making this up.

  • (cs)

    Looks like a failed attempt at creating a finite-state-machine...

    I wonder if this programmer has ever heard of the term "look-up table" if indeed he was trying to create an FSA.

  • (cs) in reply to rogthefrog
    rogthefrog:

    My guess is that that "developer" has an XML template for the function and runs a script to generate the actual code for all 95 or so. That makes it very easy to add new functions as new ASCII codes are added to the lower 127. ...<charfunc><char>
    This goes through a DOM parser that generates brillant code. SO MUCH TIME SAVED!


    Probably something like that, but you've got to admire the fact that only the original ASCII alphabet gets treated. Anything outside it is simply skipped. Let's hope this piece of code was not used in some product intended for other language markets. Can you imagine the despair of the users in that case?

    Perhaps the response would be to fill up the table with all Unicode points until 0xFFFF (just leaving out the Koreans and the Chinese, but still serving those that write in Old Italian and Linear B).
    </char></charfunc>
  • (cs) in reply to Meddler
    Meddler:
    Mung Kee:
    Meddler:
    They'd at least be tolerable if they were pure acronyms (pronouncable) and not just initialisms.  Like, uh, RELOBLOPOCOCO.  That's much more fun to say!


    Oh, you mean pronouncable like "SQL?"


    Some still insist on saying each letter instead of using the established pronouncable acronym we all love.  It's interesting how one pronunciation becomes preferable to another. We could be going around saying "I love how easy it is to install my squall in windows."   And sometimes the word doesn't quite fit - around here people say NMEA (a type of GPS signal) as "nee-ma" as if it's NEMA.

    What are you talking about, FF8pc was a bitch to install and never ran at more than 18 fps. ;_;

    Alex Papadimoulis:

    Gene Wirchenko:
    Please do not strain for acronyms.  It is undignified.  (See the rest of the IT industry for copious examples.)

    Note that my attempts at such acronyms are satire. I much loath the absurdity of IT buzzword/acronyms. AJAX is one of the most painful examples of these. If killing its creator would undo the word, I swear, I would do it ten times over.



    Wait, you mean Google didn't invent a way to use javascript and xml to clean your sink? I've been had! Here I was hoping it would usher in a new age of dynamic, self-modifying bathroom tile. >(
  • Raoul Duke (unregistered) in reply to Gene Wirchenko

    I agree with Gene about the acronyms, stop it now please for fucks sake.

    Sincerely,

    Raoul

  • (cs) in reply to Dan F

    I can't make any sense of that LetFoo at all. Hmm. We only call it when currentchar is foo. So we set j to 1 immediately. Then we set... CurrentCharvalue to the value of the character that it already has.

    Am I misreading this? Furthermore, wouldn't this be an infinite loop if you ever for any reason called it with a buffer that didn't contain any Foo, and won't it just skip past any non-Foo it sees, if you call it with the wrong index?

    I'm really not understanding this. I am not even sure it does anything at all.

  • Andy (unregistered)

    Brillant! Although at first glance this appears wasteful, in fact it is necessary for compatability with pre ANSI X3.4-1986 machines. Because of this problem, almost all european PC's using ISO 646 (1972) are incompatible with modern PC's in almost all programs, the only exceptions being this and MLCAD (1999). However it could be improved using a switch statement, as follows:
    SELECT CASE lcrBuffer.CurrentChar
    CASE ELSE:
        IF lcrBuffer.CurrentChar = "&" THEN GOSUB letAmpers
        IF lcrBuffer.CurrentChar = "@" THEN GOSUB letAt
        .....
    END SELECT

    First A-F challenge attempting post!         (<--- oneline part)

    Btw why are you guys so hard on all the noobs who post? I know it isTrue(that they make a lot of lame jokes) and stuff but can't we all just get along? You guys are forum-nazis. I hate idiots who insult people and retards who recursively insult themselves by listing themselves as a category they hate.

  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:

    Do your sarcasm detectors work?  Some so-called sarcastic remarks are actually straight responses, and vice versa.  It is hard to tell when facial expressions, tone of voice, pauses in voices, and other factors are not available.  If you think you have it down totally, you are probably fooling yourself.  I gave up on being 100% sure a long time ago.

    Sincerely,

    Gene Wirchenko



    If not even the great and magnificent Gene Wirchenko can detect sarcasm accurately, what hope does the average man have?

    Sincerely,

    Richard Nixon
  • Dwayne (unregistered) in reply to procyon112
    procyon112:
    I also like how it's not even in ASCII order, or a switch statement, so not only is each case tested for every case, but there's no hope for the compiler to optimize it in the slightest.


    That's one way to prevent timing attacks!
  • (cs) in reply to Orinocohol
    Anonymous:

    I'm amazed. Your post actually counts as meta-humour since, with a little stretching of the definitions, your own post fits happily into category F). Not that I don't completely agree with you, but still, sweet.


    Captain Obvious saves the day! Thank you, Captain Obvious!

    Congrats for your working sarcasm detector.

  • (cs) in reply to brazzy
    brazzy:
    Anonymous:

    I'm amazed. Your post actually counts as meta-humour since, with a little stretching of the definitions, your own post fits happily into category F). Not that I don't completely agree with you, but still, sweet.


    Captain Obvious saves the day! Thank you, Captain Obvious!

    Congrats for your working sarcasm detector.



    You are being sarcastic, right?
  • RobS (unregistered)

    Back on topic
    I have a few questions:

    1. did this guy get paid to do this?
    2. did he get paid by the line?
    3. is he one of those guys who got hired with a certificate and no real experience?
    4. what type of comapny allows this to happen?

    but mostly:
    5) did this start out simple and just become horribly extended over time:
    stage 1:
    <font>if</font> (lcrBuffer.CurrentChar == <font>'&'</font>)
      LetAmpers(lcrBuffer, lmpAction);
    <font>if</font> (lcrBuffer.CurrentChar == <font>'@'</font>)
      LetAt(lcrBuffer, lmpAction);
    stage 2:
    <font>if</font> (lcrBuffer.CurrentChar == 92)
      LetBackSlash(lcrBuffer, lmpAction);
    <font>if</font> (lcrBuffer.CurrentChar == 58)

    stage 3:
    <font>if</font> (lcrBuffer.CurrentChar == <font>','</font>)
      LetComma(lcrBuffer, lmpAction);
    <font>if</font> (lcrBuffer.CurrentChar == <font>'$'</font>)

    You know...product creep, bad initial design, no time to redesign...
      LetDollar(lcrBuffer, lmpAction);

      LetColon(lcrBuffer, lmpAction);

  • Yaw (unregistered)

    I sadly have to deal with this kind of crap all day at work :(

    At least now I know I'm not alone

  • (cs) in reply to zeroWS

    Anonymous:
    Anonymous:
    It has got to be computer made. While I am now fully convinced there are people out there stupid enough to do this, the chance of finding one with this amount of patience as well is next to none.


    He used to work for me. I can give you his name if you'd like.

    I am not making this up.



    I take it you're very glad he worked for you in the past tense.

    Given a skill this... lacking, the question that comes to mind is, exactly what lies and impressive buzzwords did his CV have on? If he can get a job coding, surely there's hope for me and/or my pet cat walking randomly on the keyboard to do so.

    (And I bet my cat would generate more usable code per hour too.)

  • (cs) in reply to Todd Aspeotis
    Anonymous:
    What. The. Fuck. How can you be so stupid? Like really. This just defies stupidity. Did he write a tool in some other langauge to do those Let*Equal, because it would be ironic if he had something like printf("Let%sEqual (...)\n{\tlcrCurrent += %d", szCharName, cChar); Somewhere in it.


    Pretty close, but I think you missed the closing brace.  Anyway, what you really meant was...
    printf("Let%sEqual (...) {\n\tlcrCurrent += %d\n}", szCharName, cChar);
  • (cs) in reply to RevMike
    Why even cut-and-paste?  Each of the LetFooBar functions is actually #define macro that calls the same function with an extra parameter.

    And this parameter is the ASCII value of the character?

    SCNR

Leave a comment on “Not Just Another RLB o'PCC”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article