Surely you are contradicting yourself? A standard is just that; a common way of doing something. The whole purpose of a standard is to 'remove' preference and choice.
So unfortunately if you want to standardize you need to do everything the same way. i.e. if your editing files looking at them with long indents (or re-arranged formatting based on clever display scripts) then your actually not working to standard.
'Here's t'spaces'
Simon
Dossy wrote:
[EMAIL PROTECTED]">On 2002.11.11, Peter M. Jansson <[EMAIL PROTECTED]> wrote:Indentation, like beauty, is in the eye of the beholder (which, I
think, was part of your point about the flexibility of using tabs
rather than spaces).
Exactly my point. Using spaces for indentation makes indenting an
author-only choice. Using tabs makes indentation a reader-specific
choice.
When it comes to code-readability, it should be easy to format the code
that's easiest for the reader to read. For poorly formatted code (that
which uses spaces isntead of tabs) I can easily whack ":1^M=G" in vim
and have it re-indent everything for me the way I like. It's just a
pity that if the code needs to be shared, I have to go make edits
against the original, un-reformatted file.
Anyway, it's all a matter of preference and the decision is entirely
arbitrary.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
.
-- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801
Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
