http://bugzilla.spamassassin.org/show_bug.cgi?id=3711
------- Additional Comments From [EMAIL PROTECTED] 2004-08-22 11:07 ------- Subject: Re: API change: Rename M::SA::read_scoreonly_config (and offsprings) On Sun, Aug 22, 2004 at 10:56:55AM -0700, [EMAIL PROTECTED] wrote: > Come on -- we've changed so much for 3.0, what does yet another routine name > make a difference? Do you want to carry it through till 4.0? Ok, this is > the Yeah, all the major changes were done before the pre releases came out. There've been a handful of minor ones changed since, and that's it. We don't want to change public API function names in the 11th hour... > Also, we really need to find a more efficient way of documenting our API. I > often don't have an idea which part is public and which is internal only and > what actually exists there. The *scoreonly* stuff I just discovered because > I Yeah, that's true. Typically public v private is either/both of "underscore in front of function name means private" and "no POD section means function is private". We do need to clean that up/standardize quite a bit more... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
