public/private/stable/unstable
John Arbash Meinel
john at arbash-meinel.com
Tue Aug 26 23:54:58 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
...
> And:
> _ means *either* is fine, as long as no review ever says "dont use
> symbol _GAM because its private" when the symbol is actually public but
> unsupported. So choosing "means either" will cause reviewers to know
> their symbols better, or cause them to stop commenting on usage of _
> symbols.
>
> -Rob
My personal vote is for _ == either. It is simply a way to convey to people
wanting to use the api that we don't guarantee it will be preserved without
warning. A "use at your own risk" flag.
I believe Aaron has different feelings. He felt *very* strongly that
_iter_changes was never-ever supposed to be used by anyone without pushing to
get it "public" first. My feeling was that it was there, better than
everything else, and we just wanted some time to polish it before we committed
to backwards compatibility.
I've also never had much problem with making plugins compatible using
"getattr()" style handling.
Unfortunately, I think we need to wait another week for Martin/Andrew to come
back before we can get a consensus. And this is deep in a thread so they might
miss it.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFItInCJdeBCYSNAAMRAguOAJ9nHI7WVKVGYqGwuv++jJSsj18VhACeM1ks
bXVYC9q81243gmMZEnmW358=
=pvGK
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list