I agree with you, and it seems that much of the existing jdbc code is 
formated that way.  But before starting a thread on what everybody 
prefers as their java format, let me first ask the question:

Should the jdbc java code use the same formatting as the C code?

If the answer is yes, then we know what the format is going to be.  Else 
we can have what I am sure will be a long religious battle on what style 
would be best for the java code.

My personal vote is to stick with the same format as the C code.  While 
personally I think a different format would be better, I don't think it 
is worth the hassle, and I can live with the existing format.


Dave Cramer wrote:
> Well, my vote would be for a 2 space indent.
> Dave
> On Tue, 2001-09-04 at 16:59, Tom Lane wrote:
>>Barry Lind <[EMAIL PROTECTED]> writes:
>>>I am OK with the style used for the C code.  However I would like the 
>>>following additional step done for the java code:  replace all tabs with 
>>I disagree with this, because then we are *not* applying the same coding
>>standards in the backend and in JDBC.  If you want to propose that we
>>dispense with tabs throughout the system, feel free to propose that ---
>>but it was shot down last time and likely will be again.
>>I personally concur that four-space tabs is a horrible standard, and
>>would much rather see us using eight-space tab stops.  But I haven't
>>been able to obtain any significant consensus for that view.  Some
>>developers apparently use editors where a physical tab character needs
>>to equal the logical indent amount...
>>                      regards, tom lane
>>---------------------------(end of broadcast)---------------------------
>>TIP 5: Have you checked our extensive FAQ?
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


Reply via email to