Re: Reformatting libobjc C code?

[Nicola Pero <nicola at brainstorm dot co dot uk>]

> > Would reformatting the C code in libobjc to be closer to the coding
> > conventions be useful or would it cause problems synchronizing with
> > external versions?
> > (Reformatting, mostly adding whitespace.)
> 
> Yes, it would be much appreciated!  As far as I know, there are no
> external versions with which to sync (Apple does not use GNU libobjc),
> but it would be convenient to check this in after the current
> round of warnings patrol goes in.

There are external versions :-) just not Apple ones :-)

eg, gnustep supplies a standalone libobjc to use with old gccs which don't
have a shared version of libobjc - it's now unmaintained and basically
deprecated for everything newer than gcc 2.95 ... it's definitely much
much better to work all together on the libobjc shipped with gcc - it's
both better because we share the work with other Objective-C users, and
it's better because it's simpler for end-users - they don't have to
install a custom runtime library.

Last time I looked at Swarm, I think that Swarm too had its own libobjc
`branch' which is shipped with Swarm itself (I think they would be better
merge any improvements they did into the standard gcc's libobjc, and start
using/contributing to the default one rather than keeping their own
`branch').

In general, I would consider proper formatting an improvement, and I don't
think we should stop making improvements simply because someone else has
got an external version somewhere on the net.  So - I am quite in favour
of reformatting properly.