Real-time programming safety in Java and Ada
ACM SIGAda Ada Letters
Object-oriented processing of Java source code
Software—Practice & Experience
Explicitly and implicitly teaching Java best practices across the undergraduate curriculum
ISICT '04 Proceedings of the 2004 international symposium on Information and communication technologies
Making frameworks work: a project retrospective
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Improving the tokenisation of identifier names
Proceedings of the 25th European conference on Object-oriented programming
Mining Java class identifier naming conventions
Proceedings of the 34th International Conference on Software Engineering
| Hi-index | 0.00 |
From the Book:The syntax of a programming language tells you what code it is possible to write-what the machine will understand. Style tells you what you ought to write-what the humans reading the code will understand. Code written with a consistent, simple style will be maintainable, robust, and contain fewer bugs. Code written with no regard to style will contain more bugs. It may simply be thrown away and rewritten rather than maintained. Our two favorite style guides are classics: and Kernighan and Plauger's The Elements of Programming Style. These small books work because they are simple-a list of rules, 'each containing a brief explanation and examples of correct, and sometimes incorrect, use. We followed the same pattern in this book. This simple treatment-a series of rules-enabled us to keep this book short and easy to understand. The idea is to provide a clear standard to follow, so programmers can spend their time on solving the problems of their customers, instead of worrying about naming conventions and formatting.