Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Namespace specification #31
The drivers and their parts (like buyer, card, etc) uses different methods to create the namespaces. For example, if we have the driver
I think that need to use only one of these ways:
or may be third
And I propose the first (
Thank you for your input, @dionys.
This issue annoys me too, and maybe I didn't think it through when I was first creating the classes :) But still, I'm not quite sure of what would be the best way to go.
The third way seemed too long for me. The second way would seem messy with internal namespaces, so that
Finally, the first case.. my issue with it is that a typical, complex, driver would have a directory more or less like this:
That is also weird for me. When it gets installed, the driver won't have a directory of it's own, it will be scattered around the same folders as the other drivers.
Well, anyway, these are my thoughts on the issue. Do you still think
Hmm. You’re right.
Taking in response to your comments I see 2 ways: