blocks|key|954019|text|这个问题出现在我工作的源代码库中的大多数情况都是由于制表符和空格的混合造成的。在一个人的编辑器中，每4个字符设置一个制表位，看起来很好，但在另一个人的系统中，有2个或8个空格键，看起来很糟糕。您可以随心所欲地重新排列这些数字；有些文件无论如何都会乱七八糟。改变间距对于合并来说是一个巨大的痛苦，所以它永远不会得到修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|954020|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Most cases of this problem that appear in the source base I work on most of the time are because of intermixed tabs &amp; spaces. In one person's editor, with tab stops set every 4 characters, it looks fine, but on another person's system with 2 or 8 space tabs it looks awful. You can rearrange those numbers however you want; some files are messed up regardless. Changing the spacing is a giant pain for merging down the road, so it just never gets fixed.

blocks|key|705367|text|如果你用php编写代码，很容易就会有“不好缩进”的html，我想说的是，对php来说，整齐地缩进比它吐出的html更重要……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|705368|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

it's easy to have 'poorly indented' html if you're coding in php, i'd say its more important for the php to be neatly indented than the html it spits out...

blocks|key|3020926|text|除了Carl's+observation之外还有两点|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3020927|3020928|“适当”的缩进是一个约定和语言结构的问题。|unordered-list-item|3020929|签入到源代码控制中，如果没有事先咨询，可能会被认为是非常糟糕的。|3020930|3020931|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2472553/why-is-there-so-much-poorly-indented-code-out-there/2472572#2472572^0|2|I|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Two points in addition to <a href="https://stackoverflow.com/questions/2472553/why-is-there-so-much-poorly-indented-code-out-there/2472572#2472572">Carl's observation</a>:

<ul>
<li>"Proper" indentation is a matter of convention and language structure.</li>
<li>A check in to source control that consists only of changing the indentation of a bunch of lines is likely to be viewed very poorly without prior consultation.</li>
</ul>

blocks|key|3021002|text|为什么人们不能穿着得体呢？人们做饭的时候为什么不加适量的大蒜呢？为什么每个人都听奇怪的音乐？你的问题假设了一个权威，它定义了我还没有看到的正确性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3021003|除此之外，我喜欢在整个文件中保持一致格式的代码。如果你使用1个制表符或3个空格，我并不介意，只要你一直使用它。同一条线上的大括号或单独的一条线也是一样的，不要在意，只要保持一致即可。|3021004|我个人使用VS，它开箱即用，为我自动格式化所有内容，我对默认规则集非常满意。|3021005|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Why don't people dress correctly? Why don't people use the right amount of garlic when they cook? Why does everyone listen to weird music? Your question assumes an authority that defines correctness which I've yet to see.

Besides that, I do like code that is consistently formatted across the file. If you use 1 tab or 3 spaces I don't really care as long as you use it consistently. Same with braces on the same line or a line on their own, don't care, just be consistent.

I personally use VS which out of the box auto-formats everything for me and I'm completely happy with the default rule set.

blocks|key|4488850|text|人们普遍认为，编码风格是“个人选择”的问题，一种风格和另一种风格一样好。我不认为这一定是真的。最近为accu+(仅限会员在线使用)撰写的一篇文章建议，可以将各种快速阅读技术应用于代码布局，使其更易于阅读和理解。毫无疑问，关于人类获取信息的方式有大量的数据，但这篇文章是我第一次看到将其应用于代码布局。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4488851|可能有相当多的信息表明，某些代码布局更适合人类阅读和理解，但我见过的(许多)论点都没有提到这样的信息，而且通常涉及为人们已经习惯的风格辩护。|4488852|entityMap|0|LINK|mutability|MUTABLE|url|http://accu.org/index.php^0|1E|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

It's widely accepted that coding style is a matter of 'personal choice' and that one style is as good as another. I don't think this is necessarily true. An article recently written for the <a href="http://accu.org/index.php" rel="nofollow noreferrer">accu</a> (only available online to members) suggests that various speed reading techniques can be applied to the layout of code to make it easier to read and understand. There are undoubtedly masses of data on the way humans take in information, but this article was the first I've seen applying it to code layout.

There may well be considerable information demonstrating that certain layouts of code are more suitable for humans to read and understand, but none of the (many) arguments I have seen refer to information like this, and generally involves defending the styles people have become used to.

blocks|key|4488759|text|也许这些程序员的“适当缩进”的想法与你的不同？也许你的代码看起来像一堆他妈的乱七八糟的缩进？认真地说，每个程序员似乎都有自己关于“适当”缩进的想法，并且有一种奇怪的倾向，就是抨击别人的缩进样式是“错误的”。从互联网开始(和更早的时候)，缩进就是一个突出的话题。不需要再给火上浇油了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4488760|话虽如此，你使用哪种风格相对来说并不重要。在整个项目中始终使用相同的缩进样式是非常重要的。当团队中的每个程序员都试图将自己的风格强加给团队中的其他成员时，最常见的混乱就开始了。结果是一个丑陋的混杂和不合适的缩进样式的混乱，让人发疯。这就是为什么为每个有超过几个程序员参与的项目建立编码标准是很重要的。我再说一遍--选择什么编码标准并不重要，一致性很重要。|4488761|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Maybe simply those programmers' idea of "proper indentation" is different than yours? Maybe YOUR code looks like an ugly mess of f***ed up indentation to them? Seriously, each programmer seems to have his own idea of "proper" indentation, and a curious inclination to bash other people's indent styles as "wrong". Indentation has been a prominent topic of flame-wars from the beginning of Internet (and earlier). No need to add more fuel to the flame.

That all being said, which style you use is relatively unimportant. It is much more important to use consistently the same indent style throughout the project. The most common mess starts when each programmer on the team tries to use and force his style on the rest of the team. The result is an ugly mess of mixed and unfitting indent styles that drives people crazy. That is why it is important to set up coding standards for every project that has more than a few programmers on it. I repeat - what coding standards are chosen is unimportant, consistency counts.

The more I browse the code to open source projects in languages that aren't Python, the more I realize that it seems a lot of programmers don't believe in proper indentation. (I won't mention any projects specifically to avoid having anyone take this question too personally.) Usually code is indented, but in a way just different enough from the standard style that it drives me crazy, especially in old/crufty code. I've noticed that when I write in C-like languages, I tend to indent correctly as religiously as when I'm writing in Python, with the exception of debugging code that I actually want to stick out like a sore thumb. Given how easy it is with a modern IDE to fix incorrect indentation, what are some rationales for not religiously keeping indentation in sync with braces?

Why is there so much poorly indented code out there?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我越多地浏览代码以使用非Python语言打开源代码项目，我就越意识到似乎很多程序员不相信适当的缩进。(我不会特别提到任何项目，以避免任何人对这个问题过于个人化。)通常代码是缩进的，但在某种程度上与标准样式完全不同，这让我抓狂，特别是在旧的/粗糙的代码中。我注意到，当我用类C语言编写时，我倾向于像在用Python编写时一样严格地缩进，除了调试代码之外，我实际上想要像一个痛苦的拇指一样突出。考虑到使用

问为什么会有这么多缩进不好的代码？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么会有这么多缩进不好的代码？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么会有这么多缩进不好的代码？
EN