TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why You Should Always Comment Your Code

2 点作者 deconq超过 12 年前

1 comment

mseebach2超过 12 年前
That's an extremely bad example - why would cat <i>ever</i> fall through to dog? At least come up with a situation where fall through makes sense.<p>Generally, IMO, it's a much better idea to use meaningful constants and method names.<p>So the code becomes:<p><pre><code> switch(action) { case CHECK_AND_FOO: check(); case FOO: foo(); break; default: llama(); } </code></pre> Now, Joe would not only know not to add in a break, but also <i>why</i> - all without adding a single comment.