On Mar 23, 2010, at 11:42 AM, Pieter de Bie wrote: > This is a good idea. One thing that I'd like to see is to declare > those private methods in a class extension in the implementation file. > I've done this only in one or two files myself, but for new code we > should really do that.
When I create a new extension for a class should I put all the preexisting private methods in it? If so should that be in a separate commit? --Nathan http://brotherbard.com/ To unsubscribe from this group, send email to gitx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
