Oh my god. Are you really claiming that multiple entry points, and overlapping code that must be executed backwards to function is an example of good design???
If you ever came to work at our shop, I would never, EVER let you write so much as a macro! :-)
I did not say backwards. However, the rest is correct and indeed it is excellent design! It is just this kind of excellent design that allowed Visicalc, the first spreadsheet to work in just 64k of memory and which allowed Lotus to do just about everything a spreadsheet needs to do in a mere 256k. Reuse of code is an efficient and proper programming practice when resources are limited or one wants or needs concise code. Indeed, even the garbage code in MS products does reuse much code. Subroutines were created just for that purpose - to reuse code in different parts of a program. Assembly programmers took this one step further and not only reused subroutines but used different insertion points to get different operations from the same code. Some would even target entry into the middle of an instruction to get a different instruction. This is also done in the genetic code in some instances by reading the DNA codons out of phase (ie not starting at the first of the 3 bases but at the 2nd or 3rd base) thus producing a completely different instruction. To develop such a system of reusing code is completely impossible to do at random.