Subject: Re: [boost] coding conventions
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-01-04 10:33:46
> I have always been curious about that. To me it makes *no* sense to
> use spaces for indentation. I always use tabs for indentation and
> spaces for alignment, my reasoning is that you can set tabs to be any
> size you want in your editor, one space if you wish even, and spaces
> for alignment just makes sense, for example:
If code is written with two-column tab stops and viewed with eight-column tab stops, the code can easily exceed the display or printed page width. With spaces, the original author's indentation is preserved, so the line lengths can't exceed 80 columns (presuming the original was so constrained) regardless of the width of a tab stop.
OTOH, I understand that using tabs for indentation does allow each person to view a file as preferred without affecting other's view of the same file (ignoring line length problems, of course).
As was noted by Daniel James, for Boost at least the issue is moot.
Rob Stewart robert.stewart_at_[hidden]
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.