通过代码分离技术三种方法的介绍和比较，解决了现存的代码混乱问题。
This paper solves the question of code mixed through introducing and analyzing three methods about code separation technique.
它也可以避免内部FLASH存储器的偶然擦除和编程引起的代码混乱。
It also protects against code corruption resulting from accidental erasing and PROGRAMMING to the internal FLASH MEMORY.
生成的代码通常过于简单，或者因过多的信息(工具所需的)而造成代码混乱。
Generated code is often too simplistic, or cluttered with extraneous information required by the tool.
在许多情况下，更改方法签名以使合作者成为参数将会在方法的原始调用者内部产生混淆的、未经试验的代码混乱。
In many cases, changing the method signature so the collaborator becomes a parameter will result in a confusing, untested snarl of code inside the method's original callers.
每个人都负责这一事实消除了无代码所有权所带来的混乱。
The fact that everybody is responsible negates the chaos that ensues from no code ownership.
每个人都负责这一事实消除了无代码所有权所带来的混乱。
The fact that everybody is responsible counteracts the chaos that ensues from no code ownership.
为了利用泛化算法而对代码进行移值的时候，这些不透明因素可能会造成混乱。
These elements of nontransparency can cause confusion when migrating code to take advantage of generic algorithms.
如果您收到的代码非常混乱，该怎么办？
您再也不用搜索全部代码去找出不正确的或者混乱的状态。
You never have to go searching through code to find the incorrect or misordered state change again!
通过使不同的开发者在各自的领域发挥出自己的长处，我们就不会有混乱的代码或非常丑陋的外观和感觉。
By letting the different developers excel in their own areas, we don't have mucked-up code or a look and feel with a serious case of the uglies.
这两者相互矛盾，因为用户体验都在于小的细节，而这些小细节最终毁于他们的不忍心使代码变得混乱。
The two goals are at odds, because the user experience is all about the little details, and those little details all end up being messy bits of code you would rather not have to write.
这比清单1中混乱的导入和代码更改更好，您说呢？
This is much better than the messy imports and code changes from Listing 1, wouldn't you say?
省略可选的分号意味着更少的符号输入和更少的符号混乱。把各个语句隔离到它们自己单独的行上面可以提高你的代码的可读性。
Omitting optional semicolons means fewer characters to type and fewer characters to clutter your code. Breaking separate statements onto their own lines increases your code's readability.
这样可以减少阅读代码时的视觉上的混乱。
Michael建议，虽然重构和重写都会使代码更加清晰，但是这两种技术都会导致现有系统的混乱。
Michael suggested that, though refactoring and rewrite might lead to cleaner code however, both the techniques bring chaos to the existing system.
就像在传统面向对象编程中实现的那样，这些关注点是作为单独的实例处理的，有可能在应用程序类中产生互不相关的代码(就是混乱)。
As implemented in traditional object-oriented programming, these concerns are handled as individual instances, introducing potentially unrelated code (that is, clutter) into application classes.
打乱顺序最糟糕的结果是造成数据混乱，最幸运的结果是大块样本同步代码出现bug。
What results instead of order is, at worst, chaos and, at best, large blocks of boilerplate synchronization code prone to bugs.
Mary：“这个代码很混乱。
与任何原型一样，我们的要求不仅限于初始设计，所以代码变得越来越复杂和混乱。
As with any prototype, our requirements kept creeping in past the point of initial design, so the code got messy.
业务逻辑代码使用服务定位器避免目录查找代码变得混乱，因此它很容易理解。
Business logic code that USES a service locator avoids becoming cluttered with directory lookup code, and so is easier to understand.
按照字面的意思，代码折叠将允许您折叠代码片段，这样编辑器不会变得过于混乱。
Code folding lets you literally fold pieces of code so the editor doesn't get too cluttered.
我觉得行内注释非常重要，有助于创建可见的空白，而且不会让代码看起来混乱不堪。
I think inline comments are quite important, and aid in creating visual whitespace as well which prevents the code from appearing cluttered and messy.
在需要样板代码的地方，它是极为有用的工具，可以帮助源代码树消除那些对应用程序的操作毫无用处的混乱。
It's an extremely useful tool in situations where boilerplate code is required, helping to keep your source tree free of clutter that contributes nothing to the operation of the application.
如果代码非常混乱以致于需要逐行注释，那么更有利的方式是首先简化代码。
And if your code is such a tangle that you need a comment for every single line of it, you'd probably profit from making it simpler in other ways first.
它整理了方法中的代码，该方法实际上是检索和使用bean的，因此使得代码不是那么混乱，可读性稍强一些，如下所示。
This cleans up the code in the method that actually retrieves and USES the bean, thus making the code a bit less cluttered and more readable, as shown below.
如果出现错误程序代码，浏览器中呈现的网页布局就会很混乱，用户会由于这个原因离开网站。
Incorrectly written program code will make your site users close it immediately due to its bad appearing in their browsers.
原则上，我们要把这些接口定义包装在包含文件中，避免他们在源代码中被搞混乱了。
In practice, we will wrap up these interface definitions in include files and keep them from cluttering up the source code.
减少这些混乱的方面(认知的负荷)允许每一种类型的软件消费者感觉更好关于一些代码。
Reducing these confusing aspects (cognitive load) allows software consumers of every type to feel better about a block of code.
减少这些混乱的方面(认知的负荷)允许每一种类型的软件消费者感觉更好关于一些代码。
Reducing these confusing aspects (cognitive load) allows software consumers of every type to feel better about a block of code.
应用推荐