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

rewrite/discuss coding guidelines #7

Open
cebe opened this issue Nov 18, 2011 · 0 comments
Open

rewrite/discuss coding guidelines #7

cebe opened this issue Nov 18, 2011 · 0 comments

Comments

@cebe
Copy link
Member

cebe commented Nov 18, 2011

I think we should rewrite/discuss our coding guidelines.
After this discussion with @creocoder I thought about the E prefix and came to the conclusion that I'd miss it.

I think the E prefix was quite a good thing to mark extension classes as just that, extensions and not part of my project.
So why do we need that? Not really for class name conflicts but for having a scope.
Yii core classes have the C, extensions the E and my own projects classes are without prefix.
This is what I do when extending yii core classes: create a class with the same name but without the C prefix. Same thing could be done with yiiext extensions when they have the E prefix. If the extension I want to use does not fit all my needs exactly (which is the common case I think) I can extend it the same way I extend yii core classes.

btw: guidelines should also appear on yiiext.github.com

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