Firstly hoever, Id like to draw your attention to the magazine youre reading this in and to kuru, who approached me about writing these articles. This is due to C's cryptic nature. And so structure and style come into the picture. This however, should NOT be the case, as structure and style are very important to the readability, and the ability to understand the inner workings of the code. However, many people may not know the other two elements of the complete Pasta Theory of Software.
Lasagna code is used to describe software that has a simple, understandable, and layered structure.
Lasagna code, although structured, is unfortunately monolithic and not easy to modify. An attempt to change one layer, while conceptually simple, is often difficult in actual practice. We need to go beyond the condemnation of spaghetti code and to the active encouragement of ravioli code. So obviously, by that document, OOP is the way to go, and IMHO it is, but thats a totally new document. Simply put, structure is a way of formatting your code such that it is easy to read, and simple to follow, and pleasing to the eye.