i'm browsing this shit daily

Come home from work
open up /prog/
realize there's no programming discussion going on
refresh for the next 3 hours
masturbate, sleep

>>39
Improved:

while (troll)
        FuckMe.muttered = 1;

FuckMe.muttered = 1;
while(True);

>>42
wtf was I thinking? I need some sleep. Troll away fellas

>>21
I am an anarchist functional programmer. The State is illegitimate.

                       _.-------.
     ----------------''       ,-.`-----.
                             ( X )      `-.
                              `-'  ,---.   |
                                  .     `---       ,----
    -----------------------.       `-.            .
                            `---------`   ,--+-----`----
                                         ;    :
                       Can I suck your   +----;
                       dich today?        `--+----,----
                                                 (
                                                  `-----

>>45

if (meme.forced == True && humour.value = Null){
    while(True){
        post(dich_snake);
        }
}

>>46

I'm not sure why I'm so adamant about not tagging that

>>46
✔ Ridiculous indentation style
✔ Lack of [code] tag
✔ use of True and Null, instead of TRUE/NULL (assuming C source with #define TRUE 1 or similar), true/NULL (C99, or possibly Sepples), or even true/null (assuming Javascript)
✔ Pointless explicit comparison with boolean constant
✔ Poster is trolling

TROLLAN QUALITY

>>48
✔ Assigning Null to the condition of an if expression

sigh... Once again I have to improve your disgusting failed code
>>46

while(meme.forced && !humour.value)
        post(dich_snake);

>>46
if (meme.forced && !humour.value) while(1) post(dich_snake);
there i fixed it

>>51
no you just slaughtered it some more

>>50
THE LOOP CAN BREAK IF I CHANGE THOSE VARIABLES IN ANOTHER THREAD!

>>53

class meme{
    private:
        char*value;
        bool forced;
        int  humour;
    public:
        meme(char*v_value, bool v_forced, int v_humour){
            if(value = v_value == NULL){
                forced = true;
                humour = -1;
            }
            else{
                forced = v_forced;
                humour = v_humour;
            }
        }

        int post(char*v_board){
            if (value){
                if ((forced && humour.value <= 0) || !strcmp(v_board, "prog")){
                    while(true) dich_snake.post());
                }
                else{
                    cout << value << endl;
                }
                return 1;
            }
            return 0;
        }
};

>>53

class meme{
    private:
        char*value;
        bool forced;
        int  humour;
    public:
        meme(char*v_value, bool v_forced, int v_humour){
            if(value = v_value == NULL){
                forced = true;
                humour = -1;
            }
            else{
                forced = v_forced;
                humour = v_humour;
            }
        }

        int post(char*v_board){
            if (value){
                if ((forced && humour.value <= 0) || !strcmp(v_board, "prog")){
                    while(true) dich_snake.post());
                }
                else{
                    cout << value << endl;
                }
                return 1;
            }
            return 0;
        }
};

>>55
Forgot you're humour-- in meme::post.

>>53
Well, perhaps that's how it ought to be.  Indeed, if the meme does become humorous, or magically obtains non-forced meme status somehow, you would need to change these properties in another thread.

>>55
Made a patch for you:
--- a/>>55
+++ b/>>55
@@ -19,7 +19,7 @@
         int post(char*v_board){
             if (value){
                 if ((forced && humour.value <= 0) || !strcmp(v_board, "prog")){
-                    while(true) dich_snake.post());
+                    while(dich_snake.post());
                 }
                 else{
                     cout << value << endl;

This will allow for better error handling; with a change to dich_snake.post() so that a nonzero return value indicates a successful post, the loop will terminate e.g. when the thread is closed.

(Incidentally, that line had an error, perhaps you were already intending to implement this?)

RE: Post >>46

While Dich Snake analysis is burgeoning and exciting area of work, I am dismayed that the work in this field is merely retreading old ground.

Is Dich Snake posting based only on the idea of it being an unfunny forced meme? No! That is a foolish stance to defend. It's very clear that those reasons are attributes of Dich Snake, and not causes.
When I proposed the first model of Dich Snake propagation I was young and looking only to get my name out and cement grant funding- a foolhardy need to distinguish myself at the forefront of Dich Snake study. The entire field has suffered for it.

I disavow the ideas put forth in my post (>>46), and I stress that all programs and algorithms henceforth avoid that development legacy.

Thank you.

>>59
propagation
IHBT.

>>60
Neither have I