Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purpose of namespace #31

Open
CroniD opened this issue Jul 6, 2017 · 0 comments
Open

Purpose of namespace #31

CroniD opened this issue Jul 6, 2017 · 0 comments

Comments

@CroniD
Copy link

CroniD commented Jul 6, 2017

Hi there,

Namespace and Class directives are basically aliases for each other (regarding the implemenation), which is confusing, because a namespace may be considered as a construct which contains multiple classes. Kinda like a grouping feature.

The documentation (README.md)

A namespace can be used in more than one file (for example, when plugging more functionality to an existing class).

doesn't reflect that Namespace and Class are the same and the implementation doesn't enforce the documented behavior.

Also I think Namespace and Class should use different templates to help differentiating each other visually if desired.

Best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant