Thanks Adam!
Before we start creating a list, we should think of a procedure that will
make sure it is kept up-to-date. It makes no sense if we create the list now
only to find that a year from now, when we need it, it's outdated.
The two most important questions to me at this point are:
- Were
On Mon, Jun 15, 2009 at 6:16 AM, Berend-Jan Weverskyli...@chromium.org wrote:
Before we start creating a list, we should think of a procedure that will
make sure it is kept up-to-date. It makes no sense if we create the list now
only to find that a year from now, when we need it, it's
I was afraid this would turn out to be difficult. Is there any way we might
be able to diff what parts of the code get compiled in the different builds
and auto generate a list? #defines might make this list rather long, but we
may be able to go through the list once and identify known differences
On Thu, Jun 11, 2009 at 8:59 AM, Berend-Jan Weverskyli...@chromium.org wrote:
All in all this means that it would be very useful to maintain a list
of implementation and design differences between the various ports. I
am looking for practical and efficient ways to create and maintain
such a
