Ahh cool, good to know!
On Wed, Feb 23, 2011 at 9:38 AM, Eric Merritt <[email protected]>wrote: > I was curious so I looked into the edoc docs. It seems that we don't > have to have the private on unexported functions. This is going to > clean up my docs a bit. > > @private > Marks the function as private (i.e., not part of the public > interface), so that it will not appear in the normal documentation. > (If "private" documentation is generated, the function will be > included.) Only useful for exported functions, e.g. entry points for > spawn. (Non-exported functions are always "private".) The content can > be used as a comment; it is ignored by EDoc. > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
