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

Replace PRIVATE and PUBLIC by EXPORTED and… humm… not exported? #15

Merged
merged 2 commits into from
Sep 10, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ Table of Contents:

***
##### Group functions logically
> Try to always separate **PRIVATE** and **PUBLIC** functions in groups, with the public ones first, unless it helps readability and code discovery.
> Try to always separate **unexported** and **exported** functions in groups, with the exported ones first, unless it helps readability and code discovery.

*Examples*: [grouping_functions](src/grouping_functions)

Expand Down Expand Up @@ -255,7 +255,7 @@ Erlang syntax is horrible amirite? So you might as well make the best of it, rig

***
##### Write function specs
> Write the **-spec**'s for your public fun's, and for private fun's when it adds real value for documentation purposes. Define as many types as needed.
> Write the **-spec**'s for your exported fun's, and for unexported fun's when it adds real value for documentation purposes. Define as many types as needed.

*Examples*: [specs](src/specs.erl)

Expand Down