I mean, returning non-zero exit status on error is just good practice. It even managed to evaluate to the same numerical value as EXIT_FAILURE when I tested it on my machine (gcc 11.4.0 linux x86-64), although I’m not sure if that’s always the case or if it’s undefined behavior.
AFAIK they’re not seriously considering it as a keyword, but they agreed that in all discussion about the semantics of exceptions they will use “yeet” as a placeholder for the keyword, so people will actually discuss the semantics and not whether the keyword is gonna be “raise”, “throw”, “except” or whatever (so-called Bikeshed Effect)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
For those curious:
I’m dumb . does the program do anything?
This is FizzBuzz.
frfr
Reminds me of lolcode:
i am seething with rage
I’m not a C programmer (is this code even C?), but I anticipated seeing comments like this. 😂
It’s like watching a car crash in slow motion trying to read it. I can’t look away…
I threw up in my mouth.
Pro tip: the arguments to
main()
don’t have to be namedargc
andargv
.Also, you forgot to #define an alias for
atoi
, andnumber
,n
, andi
could’ve been named something more on fleek.Also could have takin out mains return type and used
sus chief
number
is a variable i thinkYes, as are
n
andi
. Do they not deserve ‘fleekness?’sorry i misread. i thought u meant
number
was not#define
’ddeleted by creator
Does it make me a bad person that I like this?
Edit: wait…
return ! 0 ;
wtfEdit 2: idc still like it frfr no cap
I mean, returning non-zero exit status on error is just good practice. It even managed to evaluate to the same numerical value as
EXIT_FAILURE
when I tested it on my machine (gcc 11.4.0 linux x86-64), although I’m not sure if that’s always the case or if it’s undefined behavior.This cursed code is quite well-written.
!0 is defined as 1, that’s how argv [ no cap ] works, that and the ridiculous argc check stood out as a bit off, but works
Yes.
Artistry, on god frfr 🙏🙏
And that’s how rappers became the top programmers in the industry
Can’t wait to see Lil Yachty around work
My eyes are bleeding
The path to salvation is filled with terrors and temptation
no cap
Reminds me of Rockstar. The example also implements Fizz Buzz.
That’s my favorite esoteric programming language!
I have to say, I like the substitution of yeet for return. No cap.
Rust has an RFC that wants to consider yeet as a keyword for throwing an exception, I think they’re currently keeping it as a placeholder just in case
AFAIK they’re not seriously considering it as a keyword, but they agreed that in all discussion about the semantics of exceptions they will use “yeet” as a placeholder for the keyword, so people will actually discuss the semantics and not whether the keyword is gonna be “raise”, “throw”, “except” or whatever (so-called Bikeshed Effect)
All of my returns are going to be
yeet
from now onMy code reviewers will respond to my commits with
on god 🙏
My manager will do girl math to determine my next raise
#zoom