Change for_exprs_postorder so it stops when it reaches the passed-in expression.

The initial implementation of for_exprs_postorder did not contain a check to stop
iteration when the passed-in expression was reached, so iteration would continue up to the
root of the expression tree.  A check was added at the only place where for_exps_postorder
was used, to stop the iteration.  I moved the check inside the definition of
for_exprs_postorder, so it performs the iteration implied by its name.  This change should
not have any performance impact.

I also changed the signature of resolve_type_expression to return the resolved expression,
moving the error check from the end of that routine to its sole caller.  This positions
resolve_type_expression for use in other places in functionResolution, anticipating
changes introduced by user default constructor calls.
Revert "Add dirfiles/parallel."

This reverts commit 439da92647c3af300bf91dcab0e16856c3f27a55.
Merge pull request #106 from hildeth/stopForExprsPostorder

Stop iteration in for_exprs_postorder when it reaches the passed-in expression



The initial implementation of for_exprs_postorder did not contain a check to stop
iteration when the passed-in expression was reached, so iteration would continue up to the
root of the expression tree. A check was added at the only place where for_exps_postorder
was used, to stop the iteration. I moved the check inside the definition of
for_exprs_postorder, so it performs the iteration implied by its name. This change should
not have any performance impact.

I also changed the signature of resolve_type_expression to return the resolved expression,
moving the error check from the end of that routine to its sole caller. This positions
resolve_type_expression for use in other places in functionResolution, anticipating
changes introduced by user default constructor calls.

Both changes here will bring chapel-lang/master into closer alignment with my callDefaultConstructors branch, simplifying the merge.

[reviewer: noakes]

Mike noted that there using macros for procedural abstraction is somewhat undesirable, and I agree.  This is being committed as an intermediate solution: It should not be treated as definitive.