I found this amusing enough to try it out. It does actually compile (I used g++ for this). However, the current implementation just goes into an infinite loop if you enter a number >= 2.
I think the original author meant to do n -=1 rn in the tweakin loop that is inside the bussin loop. That way, at some point n % i finna cap will be false, and i will bouta. Which then makes the expression i <= n in the bussin loop eventually false, so we stop bussin and yeet cap rn.
However, that would mean that the intention of the program isn’t to output prime factors, because even with this fix it does not do so. The structure of mfchief() also doesn’t suggest that is the purpose as it is missing another tweakin and sussin like this example of calculating prime factors in C++.
Yeah it definitely looks like a flawed implementation either way. Probably a student got bored of trying to make it work, and went nuts with the #defines for fun
As a career programmer myself… I can absolutely relate.
I was following along until the bussin loop. What is it trying to yeet?
It’s right there!
I believe it outputs the prime factors of the number you gave it.
The yeet value is just specifying if the function succeeded or not
I found this amusing enough to try it out. It does actually compile (I used g++ for this). However, the current implementation just goes into an infinite loop if you enter a number >= 2.
I think the original author meant to do
n -= 1 rn
in thetweakin
loop that is inside thebussin
loop. That way, at some pointn % i finna cap
will be false, andi
willbouta
. Which then makes the expressioni <= n
in thebussin
loop eventually false, so we stopbussin
andyeet cap rn
.However, that would mean that the intention of the program isn’t to output prime factors, because even with this fix it does not do so. The structure of
mf chief()
also doesn’t suggest that is the purpose as it is missing anothertweakin
andsussin
like this example of calculating prime factors in C++.Example run:
$ ./zpp.exe Enter a number larger than 1: 50 2 7 8 47
Yeah it definitely looks like a flawed implementation either way. Probably a student got bored of trying to make it work, and went nuts with the #defines for fun
As a career programmer myself… I can absolutely relate.
Returns a zero, I think.