this post was submitted on 03 Oct 2025
30 points (100.0% liked)

History Memes

655 readers
807 users here now

A place to share history memes!

Rules:

  1. No sexism, racism, homophobia, transphobia, assorted bigotry, etc.

  2. No fascism, atrocity denial or apologia, etc.

  3. Tag NSFW pics as NSFW.

  4. Follow all Piefed.social rules.

Banner courtesy of @setsneedtofeed@lemmy.world

founded 4 months ago
MODERATORS
PugJesus@piefed.social
Deceptichum@quokk.au
30
Just a little coding oopsie (infosec.pub)
submitted 1 day ago by PugJesus@piefed.social to c/historymemes@piefed.social
7 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] makyo@lemmy.world 5 points 1 day ago (3 children)

Wondering as a non coder, can something like that happen with modern languages?

When I learned some C++ back in the day I remember my code not working because I forgot a = in a == statement. But then it just didn’t compile and was unusable until I discovered it.

[–] acockworkorange@mander.xyz 4 points 23 hours ago* (last edited 23 hours ago)

In C/C++:

int a = 3;
if (a = 4) { printf("four");}
if (a == 3) { printf("three");}

Will yield four.

[–] piccolo@sh.itjust.works 7 points 1 day ago* (last edited 1 day ago)

Back then, it would written in assembly which is has basically no compilations rules other than be translated to machine code. So it will do litterally what you tell it to do.

[–] WiredBrain@lemmy.ca 4 points 1 day ago

If you call the wrong variable, anything is possible.