how are variables passed from functions?

[Bernard Devlin]

Assuming that this has been the behaviour of Metacard, Revolution, Livecode
(and possibly Hypercard) for 22 years (or more), it is perhaps best just
accepted as a fait accompli.  If no-one has noticed this "aberrant"
behaviour in those 2 (or more decades), then fixing it now might well lead
to problems.  IMO better for Runrev to just state emphatically that this is
how things work in Livecode.

Bernard

On Sat, Nov 15, 2014 at 5:55 PM, Mark Wieder <mwieder at ahsoftware.net> 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. In fact, it's considered bad form in ruby code to
> include an explicit return statement at the end of a method. Xtalk has
> simply been ahead of its time all along.
>
> Now if LiveCode coders would simply put return statements at the end
> of functions where they belong there wouldn't be any confusion.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
> This communication may be unlawfully collected and stored by the National
> Security Agency (NSA) in secret. The parties to this email do not
> consent to the retrieving or storing of this communication and any
> related metadata, as well as printing, copying, re-transmitting,
> disseminating, or otherwise using it. If you believe you have received
> this communication in error, please delete it immediately.
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>