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

Use protected scope or namespaces instead of private #64

Open
pigiuz opened this issue Jun 23, 2011 · 0 comments
Open

Use protected scope or namespaces instead of private #64

pigiuz opened this issue Jun 23, 2011 · 0 comments

Comments

@pigiuz
Copy link

pigiuz commented Jun 23, 2011

Use protected in order to let us extend the framework.
I encountered a high difficulty in creating custom materials because all the properties I needed were scoped as private instead of protected. Please use protected!!

If you really don't want people to be playing with the framework's internal gears my suggestion is to scope them as part of the custom namespace "arcane" or to create a new custom namespace for each specific area of the framework (ex: "arcane_materials", "arcane_geom", etc)

The same is suggested for "final"... I don't think any class should be marked as final in an alpha version

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