On 8/28/06, Shawn Erickson <email@hidden> wrote:
> I don't see the point of doing that... since it quickly becomes a
> merge/diff nightmare with existing code branches. It would likely
> have to be Apple that took such steps to decide to lock down
> development on a segment of the code base to do reformatting (based
> on their corporate code standards).
The point of cleaning up code is to improve the conceptual mapping
from the requirements to the implementation. To me the most basic
code-cleanup is reformatting, "K&R removal", variable renaming, and
documentation. Beyond this is refactoring. All of these would provide
benefit to a programming wanting to get involved in a open-source
project and long-term benefit to programmers already involved. In my
experience not willing to perform code maintenance is equivalent to
not wanting to document code.
Hold on here... I was making no statement about the merits of such
things (please don't presume that and I don't need any education on
I am questioning the feasibility of doing this from outside of Apple
without visibility into what Apple is currently doing or is planning
to do with various segments of the code. Speaking from experience you
need much better visibility into such things if you want to do
something like this without causing problems to current development
and you want acceptance of such code backing into main branches.
A dialog should be started between folks interested and Apple first to
establish the feasibility of such a thing, align it with any coding
style requirements that Apple has (best if you want Apple to pick it
up), etc. before any work begins, otherwise you will likely just be
wasting your time.
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden