*blocks your path*

*blocks your path*

Other urls found in this thread:

gist.github.com/aras-p/6224951
pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09
pubs.opengroup.org/onlinepubs/9699919799/functions/flockfile.html
twitter.com/NSFWRedditGif

goto break;

*break;*
Sorry kiddo, nothing personal

Return 0;

>true = false;

heh, nothing personnel

>not using boolean expressions for your conditions
You have a place in hell.
while(true == true)

while( false != true && true == true && false == false)

gotta cover your bases

true = true;
while (isBoolean(true === true)) {
}

Enjoy your bugs.
while( false != true && true == true && false == false && true != false)

Retard

for (;;)

there is only one universal truth

true isn't an lvalue, dumbass.

c preprocessors
gist.github.com/aras-p/6224951

>true = false;
is not a C preprocessor directive, dumbass

>#define true false

>trying this hard

*ctrl+c*
*kills your process with my trusty katana*
Maybe next time kid....

while()
*depends on ur lang

nothin personell, kid
#include
#include
#include

void handler(int blank) {
printf("\nNice try, fucko\n");
}

int main()
{
signal(SIGINT, handler);
while (true) {
int jeff = 0;
}
}

Have a break, have a KitKat™

*ctrl+\*
quit it now

#define true false

while true:
true == false && false == true

#define true (rand()&2 ? true : false)

lmao

I teleport behind you and map ctrl+c to sigkill

nufin porsanel kids

>true == false && false == true

while (1 + 1 == 2)

I unironically used this once. If basic arithmetics fail then the rest of my program doesn't have to execute anyways.

printf isn't thread-safe, this is undefined behavior

what if it turns to while(1 + ( 0 ) )

This is undefined behavior, by the way.

this
add braces around the 1+1 op

I don't like my programs running super fast for the fear of overheating the central processing unit, so I use

while not True:
pass

Meant

while not False:
pass


I am not very smart.

this senpai

goto behindyou;

for(int i = 0; i < 1; i + 1)

*blocks your thread*

for(;;)
*optimizes your path*

c noob, please explain why this si undefined

abort(-1)

while(false)
/*
entirety of source file
*/
#define false true

Yes, you seem to be really new to C.

yes, i am really new to c

Imagine you're in the middle of writing a paper then told to immediately start writing something else on the same paper.
Your paper is now a mess

>open C++ compiler
>copy code
>compile for x64 architecture
>run the .exe
>?????
>enjoy page file / RAM speed boost

This particular piece of code is daijoubu in practice.

according to posix, printf and the lot are supposed to be threadsafe, so it isn't undefined
pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09

also
pubs.opengroup.org/onlinepubs/9699919799/functions/flockfile.html
>All functions that reference (FILE *) objects, except those with names ending in _unlocked, shall behave as if they use flockfile() and funlockfile() internally to obtain ownership of these (FILE *) objects.
which spells it out more specifically

this.
I don't know why so many autists are complaining.
>muh POSIX

>fun lock file

almost as fun as "allopenissues"

>muh better performance in the 80s

Sorry, async-safe.

>mah_nigga.jpg

>supposed to be
>according to posix
lots of things are supposed to be things and thought to be posix compliant

OS will terminate this eventually right? right?

Not on any windows, no. it just freezes

According to the C operator precedence it will first add and then do the comparison so if it evaluates to 0 or false the compiler sucks and it's better not to run anyway.

no, I use it because it looks nice

while(true) {
#ifdef true
true = 0;
#endif
}

Does that matter if there's no printf in main? since a signal won't interrupt its own handler

On linux it terminates once out of ram.

I made a new script that actually crashes linux, just run it as root

while (1)

Possible in Python2. Some weeks ago I had to review some code where someone actually used that shit to get out of a loop.

Nope, ran it as root, still terminates.

>*watchdog process teleports behind you*
Nothing personel.

#include
#include
#include

void handler(int blank) {
while (true {
printf("You activated my trap card\n");
}
}

int main()
{
signal(SIGINT, handler);
while (true) ;
}

Since nobody answered correctly...
and are wrong

It is undefined behavior because it enters an infinite loop with no side-effects and no way to break out of it in one thread of execution

its weird, but this one time I had while(true) not work. So now I do shit like while(3>1)

zozzle

>he doesn't prepare for opposite day

>>It is undefined behavior because it enters an infinite loop with no side-effects and no way to break out of it in one thread of execution
That's not undefined behavior in C.