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.
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.