you probably got it pointed out in haskell-beginners, but in case not:<br><br>
<div class="gmail_quote">On Thu, Nov 27, 2008 at 7:10 PM, abdullah abdul Khadir <span dir="ltr">&lt;<a href="mailto:abdullah.ak2002@gmail.com">abdullah.ak2002@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">a) I need to put a do after else for more than one instruction (?)</blockquote>
<div>&nbsp;</div>
<div>No, the do thingy is a syntactic sugar for chaining &quot;warm, fuzzy&quot; (the &quot;preffered&quot;&nbsp;wannabe-joke-term for the presumably scary term monads/monadic) operations.</div>
<div>&nbsp;</div>
<div>it allows you to write in &quot;classical&quot; imperative/sequential style instead of chaining operations manually (using the &gt;&gt; and &gt;&gt;= operators, which the do notation translates into anyway). lookup some&nbsp;monad tutorials/docs.</div>

<div>&nbsp;</div>
<div>you are right&nbsp;in that if there is only one operation, no transformation is needed,&nbsp;so the do&nbsp;is unnecessary.</div></div>