MathGroup Archive 2009

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Return Ambiguity

  • To: mathgroup at
  • Subject: [mg97502] Re: Return Ambiguity
  • From: David Bailey <dave at>
  • Date: Sat, 14 Mar 2009 05:40:44 -0500 (EST)
  • References: <> <gpdab1$jq0$>

DrMajorBob wrote:
> Don't use Return at all. It's poor style and will encourage bad habits.
> Just say, "No!" to Return.
> Bobby
> On Thu, 12 Mar 2009 05:41:53 -0500, Raffy <raffy at> wrote:
>> How do you determine how far Return actually returns?  I have avoided
>> using this function after having difficult getting it to return to the
>> proper level of execution.
>> In general, does it return to the nearest held expression?
>> The documentation is really ambiguous.
I hate the kind of programming advice that reads like dietary leaflets, 
or a sex manual from the 1950's - full of don't's and tut-tut's!

All those commands like Return, While, Do, (but maybe not Goto!) have 
their place. Sometimes the logic of a program is more transparent using 
one of these deprecated constructs. Different programmers may prefer 
different styles, and depending on their problem, efficiency may not 
even be an issue.

A line of code at the top of a function that disposes of an unwanted 
case: If[condition,Return[$Failed]]; is at least arguably easier to read 
than an If[....] that spans the rest of the function.

David Bailey

  • Prev by Date: Re: font size
  • Next by Date: Mathematica Question - Using DSolve with Boundary Conditions
  • Previous by thread: Re: Return Ambiguity
  • Next by thread: Re: Re: Return Ambiguity