You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@subversion.apache.org by Karl Fogel <kf...@galois.collab.net> on 2000/07/11 20:11:23 UTC

Re: CVS update: subversion/subversion/svn_subr svn_parse.c

Daniel Rall <dl...@collab.net> writes:
> If functions are not not part of the public API visible to code linking
> against the module, they should *always* be static.  :)

Yup -- we're all agreed on that, I think.

To clarify: the "svn__" convention is for symbols which must be
exported, for technical reasons, but are not part of the package's
formal (published) interface.

Re: CVS update: subversion/subversion/svn_subr svn_parse.c

Posted by Daniel Rall <dl...@collab.net>.

Karl Fogel wrote:
> 
> Daniel Rall <dl...@collab.net> writes:
> > If functions are not not part of the public API visible to code linking
> > against the module, they should *always* be static.  :)
> 
> Yup -- we're all agreed on that, I think.
> 
> To clarify: the "svn__" convention is for symbols which must be
> exported, for technical reasons, but are not part of the package's
> formal (published) interface.

+1