On 2005-07-07, Peter Wang <tjaden@xxxxxxxxxx> wrote:
We need to update abi._tx for the 4.2 release. [...]
Commited.
We need a Mac guy to write a short section for MacOS X.
Added to todo.txt.
I've toned the document down as it was, frankly, embarrassing.
At least it was funny.
On 2005-07-07, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
We also need to decide if we will maintain both backwards
and forwards compatibility, or just backwards compatibility.
The former means we can't add/change/remove any (public)
symbols at all. The latter means we can add new symbols,
but we can't change or remove any.
I say stick to backward compatibility only, if only because it's
easier for us to make sure we don't break it. ;)
Isn't forward compatibility only a problem with C++ where adding a
method may completely change classes' sizes and stuff like that? I
don't think that's a problem for C.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf