Programmer Humor

19187 readers

1233 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

397

You wouldn’t get it (sh.itjust.works)

submitted 5 months ago by sjmarf@sh.itjust.works to c/programmer_humor@programming.dev

44 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] hydroptic@sopuli.xyz 2 points 5 months ago* (last edited 5 months ago)

If you want to be able to eg. (de)serialize non-public fields of a type for any reason, you'll need some way to get around the access restriction. Mocking is another use case – although it's a philosophical discussion whether you should be mocking non-public fields.

And this isn't just a Java thing, the comment you're responding to has an example in C#, and you can do something similar in a lot of languages that support runtime reflection. Barring runtime reflection support you can do pointer math if the language supports it. Access restrictions on fields are there to stop casual misuse of private fields, but sometimes you actually may want to be able to step over those restrictions if you really know what you're doing.