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

History Memes

2353 readers
1096 users here now

A place to share history memes!

Rules:

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

  2. No fascism (including tankies/red fash), atrocity denial or apologia, etc.

  3. Tag NSFW pics as NSFW.

  4. Follow all Piefed.social rules.

  5. History referenced must be 20+ years old.

Banner courtesy of @setsneedtofeed@lemmy.world

OTHER COMMS IN THE HISTORYVERSE:

founded 11 months ago
MODERATORS
PugJesus@piefed.social
Deceptichum@quokk.au
31
Just a little coding oopsie (infosec.pub)
submitted 6 months 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 6 months 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.

[–] piccolo@sh.itjust.works 7 points 6 months ago* (last edited 6 months 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 6 months ago

If you call the wrong variable, anything is possible.

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

In C/C++:

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

Will yield four.