Re: [PATCH 01/10] move some globals into a thread object

[Tom Tromey <tromey@redhat.com>]

>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:

Tom> The #defines mean that this patch also has to rename a few fields
Tom> whose names clash with the defines.

Stefan> I'd rather rename the globals (although I understand it will probably
Stefan> result in a larger patch), because I'd rather limit the impact of those
Stefan> #defines.

Ok, I will do this, but please don't let this block looking at the other
patches.  This particular patch is one of the least interesting ones of
the series.

The big reason not to do this is just that reindenting everything is
tedious.  There are thousands of spots to check for line wrapping :-(
Just thinking about it makes me want to take a different approach instead.

Stefan> If you ever create a local variable (or a struct field) named
Stefan> `current_buffer' somewhere, it might take you a good while to
Stefan> figure out why your code is misbehaving.

FWIW, newish versions of gcc give much better error messages for
problems arising from macro expansion.

Tom