how are variables passed from functions?

[J. Landman Gay]

On 11/15/2014, 11:55 AM, Mark Wieder wrote:
> I've only followed this thread sporadically because it's been a busy
> week at work, but I'm quite amused. This is the way ruby works, and if
> memory serves, go works the same way. The last statement executed is
> the current result.

That's what I get for being a one-trick pony. But it sure seems that 
having to keep track of the last result would cause a lot of non-obvious 
errors.

Bernard mentioned it might be long-standing behavior that shouldn't be 
changed, but since no one has really noticed it until now it's hard to 
tell whether it's a newly introduced bug or an established behavior. But 
as you say, if we just put explicit return statements in our code it 
will continue to be a non-issue.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com