Thank you Irv for your detailed reply.
However, does this mean: i. a behavior is a class? ii. classes are therefore not variables? iii.we can define our own handlers in parent scripts? iv. so a parent script is a class? v. and therefore a behavior is somewhat similar to a parent script? vi. and so behaviors can be used to create objects? Is this correct? Thanks in advance Genevieve >Hope that helps. The fact that behaviors can also have a "new" >handler, and the explanation of the affect of ancestors is not >important to the basic understanding of the difference between >behaviors and parent scripts. > >Basic difference: Behaviors are intended to be attached to sprites - >beginsprite and endsprite handlers called automatically, and you can >use GPDL. Parent scripts only create objects when you as the >programmer explicitly call the new handler, objects "live" until you >kill them by setting the object reference (and any copies of the >object reference) to VOID (or 0, or anything else). > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
