Crazy script-only stack question

[Geoff Canyon]

I just checked, and yeah, this me is portable between object scripts and
behavior scripts, but it seems highly unlikely that the concept itself
would be portable. i.e. it's far more often the case that a reference to
me/this me from an object's script *should* be a reference to the control
itself, not the behavior, and copy-pasting it into a behavior script would
be an error. "the behavior of me" accomplishes the same thing as "this me"
in a behavior script, and is far more clear besides.

On Tue, Jan 23, 2018 at 8:33 AM, Bob Sneidar via use-livecode <
use-livecode at lists.runrev.com> wrote:

> This Me refers to the behavior object itself, not the object using the
> behavior. That is so that scripts referring to Me can be ported to a
> behavior without modification (I assume) and Me will still refer to the
> calling object. I suppose they could have used Real Me or some such thing.
>
> I have never actually had a need to refer to the behavior object itself in
> one of it's handlers. The only use case I can imagine is if you wanted to
> send or dispatch to call a handler in the behavior, but it's already in the
> front of message heirarchy for the calling object.
>
> Bob S