Labeling your flowchart and code

Please use labels as instructed in the screencasts and lessons. Labels like, if_break, cond_label, for_break etc. It makes code easier to read for everyone else. Use the same labels in your flowchart and code. If you work in a company they will have strict coding rules for implementation and labeling etc. You can not just write any code and expect others to understand the hidden logic in your code.

About Midterm1

i) You should always start with a flow chart, as explained in the screencasts. Then make a one-to-one correspondence with assembly language from the flow chart to write your final code. It is much easier to debug a flow chart then looking at lines of code. If you have a question regarding the logic of your program then send us your flow chart, not assembly code.

ii) The midterm statement says: Use a single for loop (alternate implementation, page 15, lesson 11) and a single if statement (alternate implementation, page 9, lesson 11). Follow these instructions, otherwise you will lose a lot of points. One of the aim of this midterm is to see if you can implement alternate implements of the for loop and the if statement.