OH NO NO NO NO NO

OH NO NO NO NO NO

Attached: z97h8o0kn9p21.png (604x510, 79K)

Other urls found in this thread:

stackoverflow.com/questions/39948357/recursion-vs-iteration-with-regards-to-memory-usage
twitter.com/AnonBabble

>referencing a non existent class
Is this the power of Apple

Tail recursion optimized Lisp dialects do not have this problem.

shh, satania is sleeping

Attached: sleepy.png (329x446, 146K)

Somebody don't check cycles on supposedly DAG

*ahem*

Attached: 1553624990623.png (313x291, 134K)

>falling for meme programming languages, that dont even have a formal specification, on a meme platform
ishygddt

>acting like this is a big deal

Attached: jakes asylum.png (510x511, 641K)

Congratulations, you discovered a forkbomb/infinite loop.

>your Mac will heat up your room in no time
Has Swift been ported to the PowerMac G5?

>Implying A == B && B == A
Isint a big deal because fundamentally A cant = B if A doesn't equal anything

Go back to sleep, slut

iTODDLERS BTFO

My old 08 Mac Pro with dual quad core Xeons heated up the room. Then again so does my modern Skylake-X machine.

Who is this thot?

Isn't it just a fork bomb?

As much as id like to insult apple i don't see how's that's different from "while(true){ }"

>did you know infinite loops exist

How would this even allow compilation?

it causes the compiler to go into an infinite loop, so it really doesn't

it dosent supposed break after 100 cycles or something?

like that js crap
function fuck(){
return me();
}

function me(){
return fuck();
}
fuck()

You have other problems if you're using lisp, like autism.

in C it segfaults

Works on my machine. No error message during compilation either.
#include

int foo(void);
int bar(void);

int foo(void)
{
return bar();
}

int bar(void)
{
return foo();
}

int main(void)
{
foo();
}

In your example, to my knowledge, function calls will get pushed onto the stack until it overflows.

>In your example, to my knowledge, function calls >will get pushed onto the stack until it overflows.
nope in most compilers its supposed to stop

Attached: Screenshot from 2019-03-31 05-34-39.png (1920x1080, 253K)

it segfaults when you run it, should've been clearer. it compiles just fine

>No error message during compilation either.
This means that in addition to it running forever, it compiles with no error.

I think my O flag is allowing it run forever.
gcc -Wall -Wextra -Werror -O3 -xc - -o fork

That's good. Do you know with what breadth this feature exists?

(*whispers*)based(*whispers*)

*camera pans*

Attached: satania and raphiel.jpg (877x472, 281K)

Yours compiles, ops doesn't

ohmy!

lol python faggot.

Autism is an advantage, not a problem, normie

Baito desu

Attached: Screen Shot 2019-03-31 at 6.00.42 PM.png (908x180, 66K)

Probably tail recursion optimization

>recursion
But that's useless, isn't it?

Are apple compilers so shit that they don't even warn about infinite loops?

>running forever is not a compile error
Nice shitlang.

OP is obviously referring to XCode wasting a lot of computing resources on code that won't even compile.

It's called undefined behavior. Sorry, C doesn't have retard guards. Enjoy using js in your house where all the sharp cornors are covered with pads.

Only if a plane crashing is to you just another form of stopping.

>That's good. Do you know with what breadth this feature exists?
It's just a stack overflow check. Any language worth a shit will either do it by default or provide the option. Depends entirely on the compiler and kernel. Linux will grow the stack indefinitely until you run out of memory or hit a limit or clash with other allocations and then it's segfault city. Windows has fixed-size stacks so it will fail reasonably fast with an access violation exception which is easy enough to catch for the runtime.

That doesn't surprise me. Apple developer tools are generally always shit.

>forkbomb

That doesn't surprise me. Apple developer tools are generally always shit.

iTODDLERS BTFO

Attached: 1539588520997.gif (500x281, 1.6M)

baste

yikes

i just love how indian programmers are ruining another US company

Attached: 1421414345826.jpg (2048x1536, 877K)

based

>semple.js

it is look like python to you? you fucking cunt

does llvm/clang check for this when compiling?

Fuck off

you are all retarded
#include

void main(void) {
while(1) {
fork();
}
}

Attached: 1527917721805.jpg (720x947, 191K)

>llvm/clang
its js not C

you know recursive is less memory consuming and its faster than a while loop right tard?

>less memory consuming than a while loop
ok

thats some gay shit

stackoverflow.com/questions/39948357/recursion-vs-iteration-with-regards-to-memory-usage

read

based

no

READ TARD READ!

Attached: 69b.jpg (1218x1015, 212K)

oh no how will itoddlers recover? im now totally convinced not to buy mac

NOOOO

Attached: 858.gif (200x161, 986K)

hey thats nice tard very nice tard

Attached: proxy.duckduckgo.com.jpg (400x400, 33K)

>python- Impor
>python-Correc
>python-Impor
>Python[pxssh]
k faggot

>Caring about memory
lmao it's not 1999 anymore kid.

Why every language except C is a giant meme...

kys electron-tard

yes?

Attached: 1551288061575.gif (500x282, 539K)

I bet this sounded better in your head

based

It's more about XCode being shit for not recognising this. But XCode is actually a worse ide than the windows notepad

Xcode is better than Android Studio tho

But it works...

Attached: idiot.png (705x634, 35K)

you can't make iOS apps in Android studio

You know, thinking back, I didn't need to include the stdio header.

haha wow, i love it

What an ass.

what is satania dreaming about?

>autism
>posting on Jow Forums(nel)
user...

btfoing itoddlers

They fixed it in Swift though. Xcode is just calling Swift methods to parse and validate the class structure.

no, it's a circular dependency

based

excellent post
baste and redpilled

me

no me

But I don't have Xcode as I'm not a faggot.

Stop using 1604

oof

What is with all this sudden Satania posting. I thought Maki was the official Jow Forums girl. Is it because they both have red hair? What is it with Jow Forums and redheads?

int main(void) {
return main();
}

>Satania posting
>sudden

BBC

niggers

Based🐰

lel. can't you simply do

if (class == myself)
return


in your recursive procedure?