Re: Re: [PATCHES] s_lock.h cleanup - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: [PATCHES] s_lock.h cleanup
Date
Msg-id 200101191640.LAA23982@candle.pha.pa.us
Whole thread Raw
In response to Re: [PATCHES] s_lock.h cleanup  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Re: [PATCHES] s_lock.h cleanup
List pgsql-hackers
> Bruce Momjian writes:
> 
> > In looking at the VAX ASM problem, I realized that the ASM in s_lock.h
> > is all formatted differently, making it even more confusing.  I have
> > applied the following patch to s_lock.h to try and clean it up.
> 
> I don't believe in this patch at all.  It makes the assumption that all
> assemblers have equally forgiving lexical rules as a certain subset of
> said assemblers.  For example, the VAX code does not look at all like the
> one back when it still worked.

I agree the VAX code was changed in the patch, but the VAX person sent
email that he had to add the semicolons to make it work on his platform,
and that the original "   \n\" code did compile at all.

I believe the formatting problem was that some code had
"command;command; : lkjasfd : asldfk" while some had them spread over
separate lines, and others used \n\, all very randomly.  Now at least
they are all consistent and use similar formatting.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Trond Kjernaasen
Date:
Subject: Re: Problems with BLOBs under Windows?
Next
From: Patrick Welche
Date:
Subject: Re: Re: Getting configure to notice link-time vs run-time failures