[Xastir] compile error

[Tom Russo]

On Fri, Dec 29, 2006 at 06:44:15PM -0800, we recorded a bogon-computron collision of the <archer at eskimo.com> flavor, containing:
> On Fri, 29 Dec 2006, Mike Fenske wrote:
> 
> > I haven't seen a compile error with Xastir for a _long_ time, but
> > with today's CVS, I got one. Looks like the new code Curt has
> > added tor printing. Running SuSE 7.3 here.
> 
> Yep.  Any time you see some _new_ code get added there's a good
> possibility that CVS may become unstable until that new code is
> fully debugged or even fully completed.
> 
> 
> > maps.c:3833: parse error before `char'
> 
> That one gets me every once in a while.  The code right after the
> function header _looked_ like variable declarations, but the 2nd
> line was actually a statement.  I put another variable declaration
> after it, which some GCC compilers are happy with, some are not.  I
> moved the new line up one and things should be good now.
> 
> Suffice it to say it compiles fine here either way.

It's a new style thing.  GCC 3.x and later is happy with it, and it's 
currently in vogue to do declarations right before the variables are needed
instead of all in a block at the beginning of the function, but any gcc 2.x 
version hates it.  

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick