Re:Don't Name Classes After Patterns. Mostly
by bcrosby95 on Sunday August 23, 2020 @03:14AM
(#24250203)
I think it depends upon your project. E.g. how far do you plan to take this - would you call it an AnimalCheetah or a Cheetah? If the latter, I would err on the side of "LandAnimal". Also, if your project is 100% about animals I would probably prefer "LandAnimal" too - otherwise you're likely to end up with a bunch of classes starting with AnimalXYZ and all you're doing is adding noise to your project when everything in it starts with Animal.
[ Parent
| on HN ]
Re:Don't Name Classes After Patterns. Mostly
by caylus on Sunday August 23, 2020 @10:27AM
(#24252181)
> would you call it an AnimalCheetah or a Cheetah?
Depends on whether you're Hungarian :P
In all seriousness, I'd go with the prefix if these are part of a large flat namespace, but if there were a lot, then they should move to their own package and become `animal.Cheetah`.