-
Notifications
You must be signed in to change notification settings - Fork 6
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
Doc block guidelines #112
Comments
hm, good idea 👍 |
@radmen ..? |
...it might also make sense to always have the "NOTE" part, so even if the function didn't change from the original: /**
* @link http://php.net/manual/en/function.xxx.php
*
* NOTE: no change
*/ |
Ok, my proposal - |
I don't know if we have to document PHP's functions. I think it's more useful to describe what we change, since we expect our target to know what they're doing if they're using and feel the need for this kind of library. Personally, I'm fine with @param etc. if they're already there (e.g., if adding them doesn't slow us down0, but the description I would along the lines of:
or:
No problem! |
I'm wondering, does it really make sense to add documentation to our functions, if they're barely a wrapper to the original ones?
Unless there are gotchas, I would just leave:
If we change something apart from the name of the function itself, we could just add a note:
What do you guys think? IMHO it's much cleaner, and this way one would actually read the comment and see what's going on. No point in documenting something that most people already know and is on php.net anyway...
The text was updated successfully, but these errors were encountered: