On Tue, Jun 15, 2010 at 3:35 PM, John Ferrell wrote: > Most, may be all of us have been here before. This round I believe the > question is simply too vague. The correct answer is context sensitive. > The code I write contains information to guide ME after I have > forgotten. It would be different if I were teaching something to some > one else. It would also be different if I were turning the code to some > one else to modify/maintain, (think client/customer). There is not a > single answer that fits all. SOME structure is desirable in all cases. > Unstructured and Uncommented Spaghetti code is never justifiable. > > The rules Olin has offered are a good general case... > > Just my opinion , of course. John, I'm not sure how the question is too vague - my problem, as stated, is that on projects i've worked on with assembly code, I end up with something that's hard to read and follow, and I'm not sure how to go about structuring it any better. Hence my request for other people's methods. I'm not sure that there is much difference between hobby code and commercial code, either... if I'm working on something intermittently over a few months' time, there are bound to be parts of the code that will be revisited only after several weeks/months, and those will sure look foreign to me at first glance. And I definitely don't want to have to reacquaint myself with the ugly mess of code each time. I did get some valuable insights, and I'm going to see how I can adapt those to my situation. - Marcel -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist