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.
While I'm unsure a separate project is required, I would love to start
getting involved in the Darwin open-source projects though first just
improving code readability and documentation. Which is what I think
Almisr wants to do.
--
-Corey O'Connor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
