On Aug 29, 2013, at 6:38 AM, Tom Browder wrote:
> On Wed, Aug 28, 2013 at 10:06 PM, Christopher Sean Morrison <[email protected]>
> wrote:
> Tom,
>
> Also, note that public API changes like the one below would have to follow
> the change policy described in the CHANGES file. My gut says that it'd
> probably be a minimally impacting
>
> I wasn't worried about it because it's new and on the trunk. Does that mean
> that new public API stuff on the trunk can never change after it's introduced
> and before a release prep call? I guess I should be a bit more conservative
> with such things, but this seemed okay since it won't truly be used for a
> while.
The API can and does certainly change (per CHANGES, it happens a lot). New
functions are also okay to add. The commit changed an existing public API
function to change an argument type (replacing the char * with an enum).
That function had been pushed out in public headers in previous releases, thus
making it "published" API. We have a social contract that says we promise to
make sure little changes are simple and we'll announce major changes in advance.
This is done to balance our needs to evolve the API with 3rd party application
developer needs to have a stable API that can be trusted. If I'm a third party
code, can I fix my code with a simple regular expression replacement or will I
have to really revisit and redo the logic?
That signature change you made was probably minimally impacting, but it was
more to be aware that this policy / contract exists.
Cheers!
Sean
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
