Content deleted Content added
mark "low" -- this is a pretty minor point |
→Loop unrolling etc: new section |
||
Line 47:
The fact that there has already been a change of "looping" to "set of methods or objects" is absolutely indicitive of the problem: there is no one single solution to bad programming. The general antidote is good decomposition, but what that will look like depends entirely on the programming methodology being used: procedural models will take a different approach than object oriented models for example.
[[User:Rnickel|Rnickel]] ([[User talk:Rnickel|talk]]) 16:43, 22 July 2008 (UTC)
== Loop unrolling etc ==
I reverted the good-faith edits made by 95.199.24.203 due to a number of problems with tone and sourcing:
* The tone was non-encyclopedic; it sounded conversational and read more like personal opinion.
* There were no sources for any of the statements; a number of them appeared to be [[WP:OR|original research]].
* There were several grammatical errors.
I did preserve the mention of loop unrolling, since that seemed to me to be the most significant point raised. There could be further discussion of loop unrolling in the body of the article, although the statement that "a common practice to gain speed increase on modern computers" is egregiously untrue. In fact, manual loop unrolling has become all but extinct in the modern era as improvements in optimizer technology have removed the need for programmers to pursue these types of "speed hacks".
--[[User:Rnickel|Rnickel]] ([[User talk:Rnickel|talk]]) 17:33, 30 July 2013 (UTC)
| |||