this post was submitted on 27 May 2024
715 points (97.9% liked)
Programmer Humor
19572 readers
1438 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't know and that's the problem :(
I keep asking myself what to choose, only for changing it a day after cursing myself to choose a stupid name.
Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place. But that's also a detriment when you know what you want. You can start typing without the prefix but you'll have to go through the better suggestions of intellisense first.
Little endiant is the same thing, but in reverse. Great when needed, but bad for browsing.
Although I do have some fix I'm starting to use. But it's not applicable everywhere, and not in every language.
What I do is use module as prefix. Instead of
dialogue_file_open
, I create afile_open
in thedialogue
module, allowing either directly callingfile_open
, ordialogue::file_open
. Using intellisense on the module allow for easy browsing too!Although in OP's post I'd rather have
file_open_dialogue
as it convey the more significant meaning, being to open a file, first. Then "dialogue" is just the flavour on topFor me it's simple.
Pseudo-OOP in C which takes dialog* as a forst argument? dialog_open_file
Otherwise - make it human readable