This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Rajdeep Biswas wrote:How do I read instruction 15 into an english statement? Actually, I want to understand what the total things says after : in instructions 10, 15, 191, 22 and 25.
Any particular reason for that? If it's just idle curiosity, or an interest in what a low-level language looks like, please don't let me stop you; but I doubt you'll find much in it that helps you as a Java programmer.
There's also a risk that you might use it to increase efficiency and that's the last thing you should do. So, by all means look, but don't write your code to get things done a particular way. It's a short route to disaster.
Isn't it funny how there's always time and money enough to do it WRONG?
Articles by Winston can be found here