LiveCode does not fit OOP paradigm, it is almost procedural and imperative but it is not due to the message path.
I think we should call our "subroutines": definitions, it is a generic enough term and it has good semantics, it means something we applied a name for. So a handler, a function and a commmand are just that definitions. On Wed, Sep 22, 2010 at 2:14 PM, Malte Pfaff-Brill <[email protected]>wrote: > Hi David, > > AFAIK in procedural languages this would be a subroutine, in OOP languages > a method > > Now, in which category does liveCode fit? <g> > > http://en.wikipedia.org/wiki/Method_%28computer_science%29 > > Cheers, > > Malte_______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
