-
Notifications
You must be signed in to change notification settings - Fork 94
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
Guidance on documenting functions #36
Comments
My preference is style B. |
B, however, I usually have a reflection based description system where I say:
Just inside the function. I even do this when I don't have that system in place. But if you have a long description, it would make less sense there. |
Do we want to include a full example? Ideally with usage and other kinds of verbose stuff people might have. I've been using this style here https://github.com/shazow/dotfiles/blob/master/helpers.bash
Ideally something that parsing/extracting won't be too hard. |
👍 |
AFAIC, 'B' too, and going a little further with bashdoc.sh script: http://wiki.sourcemage.org/bashdoc Used to have a bookmark to this script website but can't find it. My 2 cts Jérémie Tarot |
Sorry for bumping an old thread!
I'm not familiar with a 'reflection based description system'. I've googled around, but don't seem to find anything that would enable me to use the |
@ingkebil Using |
What's the preferred style for documenting functions?
The text was updated successfully, but these errors were encountered: