Don't Name Classes After Patterns. Mostly

Re:Don't Name Classes After Patterns. Mostly by jzoch on Sunday August 23, 2020 @03:57PM (#24254800)

Pretty silly reply. No need to attack. I’m fairly certain code bases can’t get much bigger than the ones I’m working on. If you abandon the idea that names should be read in a natural manner why use words at all? What a silly notion.

Many different languages style guides actually prefer verbs for functions as it makes it clearer an action is taken.

Finding function names is very easy with either approach. You have bigger problems and don’t know what you are looking for if you can’t find FakeVerse instead of VerseFake. Why is LandAnimal acceptable over AnimalLand? Why choose AnimalFast over FastAnimal? There is no reason those should be chosen: sorting is a poor argument as the loss in clarity is too great.

[ Parent | on HN ]

Re:Don't Name Classes After Patterns. Mostly by heavenlyblue on Sunday August 23, 2020 @06:01PM (#24255649)

Because all namespaces in all routinely used languages are com.land.animal and not animal.land.com

So there’s no reason in naming functions any differently when Entity within the name is just another namespace.

Also I don’t really understand why have the function name “restoreDatabase” when you could just put that function as “restore” within a module called “database”.

So you’re kind of missing the whole point of where the prefixes rather than suffixes come from.

[ Parent | on HN ]