Aspect-Oriented Programming with the e Verification Language

Chapter 3. Using AOP to Organize Your Code

	What was new, though, was the realization that “patching done right” is the most natural way to understand complex systems.
	--Ivar Jacobson [22]

Unless you plan to have your entire verification environment coded in a single file (and please don’t) then you’ll have to decide, fairly early on in the design process, how you are going to map your code to files. If you are used to object oriented programming, then you are probably used to mapping entire classes to files. Class Foo probably got placed in foo.cpp (assuming C+ + code), and class Bar probably got placed in bar.cpp. You might have used header files as well as a body file, and if you did, you might have used several body files for a particularly ...