On Fri, Apr 25, 2008 at 12:26 PM, Randall R Schulz <[EMAIL PROTECTED]> wrote: > > On Friday 25 April 2008 10:17, rssh wrote: > > Oh - interesting question. I'm afraid I don't know short definition. > > Long - get Ousterhout's original 1990 USENIX paper > > http://citeseer.ist.psu.edu/ousterhout90tcl.html > > and change C to Java in item 5
As well as changing C to Java, change the paradigm from procedural to OO. To control or customize a procedural system, it is natural to write "scripts," little procedures that call system procedures. This kind of traditional procedural scripting is not very useful when working with an OO system because the system's control and customization hooks are based on OO concepts, not procedural ones. To control and customize an OO system you have to create objects and call methods. A scripting language for a Java-based system must let you call instance methods, instantiate classes, subclass existing classes, and implement interfaces. -David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
