<br><br><div class="gmail_quote">On Mon, Mar 1, 2010 at 11:31 PM, wooks <span dir="ltr"><<a href="mailto:wookiz@hotmail.com">wookiz@hotmail.com</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">The imperative guy is convinced that all will suddenly become clear</div> to those who have hitherto been having difficulty.</blockquote><div><br></div><div> In a way, this is true. It's pretty easy to follow</div><div>imperative code at the statement level. "This</div><div>puts 17 into the box called X. This checks</div> <div>whether X is zero; it's not, so we go on. ..."</div><div><br></div><div>Of course the point is that statement-level code</div><div>tracing gets you nowhwere in terms of big-picture</div><div>understanding or software design.</div> <div><br></div><div>But the students having difficulty may very well</div><div>feel that they're understanding more.</div><div><br></div><div>--DGK</div><div><br></div><div>David G. Kay</div><div>UC Irvine</div><div><a href="mailto:kay@uci.edu">kay@uci.edu</a></div> </div>