Before and after Livecode

[David Bovill]

An example of how I used them to solve a problem that's bugged me for years
- logging / debugging things like servers. You can write a server in a tiny
bit of code, but to see what is going on / wrong you want to log things at
every step - or at least the important bits - and your code ends up with
lot's of loggin bits everywhere - even if you use a library for the actual
logging code.

Now with before / after handlers - no logging code in the server - it's so
clean and simple it is gorgeous. When I want logging I add the behavior
which includes all the efore / after handlers that havve acess to all the
data and just do the logging. When I don;t want them I remove the behavior.
Nice.

On 18 July 2015 at 11:09, Richmond <richmondmathewson at gmail.com> wrote:

> On 18/07/15 12:24, Dave Kilroy wrote:
>
>> Richmond I think David is probably referring to the 'before' and 'after'
>> control structures - as in:
>>
>> "before mouseUp
>>    answer "before mouse up received"
>> end resizeStack"
>>
>> David, no sorry I've never used them (and yes they are interesting...)
>>
>>  I'm sure you are right.
>
> Richmond.
>
>>
>>
>> -----
>> "The difference between genius and stupidity is; genius has its limits."
>> - Albert Einstein
>> --
>> View this message in context:
>> http://runtime-revolution.278305.n4.nabble.com/Before-and-after-Livecode-tp4694048p4694053.html
>> Sent from the Revolution - User mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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
>