NewtonScript
| Paradigm | Prototype Object-oriented |
|---|---|
| Designed by | Walter Smith |
| Developer | Apple Computer |
| First appeared | 1993 |
| Typing discipline | Dynamic |
| Influenced by | |
| Self, Dylan | |
| Influenced | |
| Io | |
NewtonScript is a prototype-based programming language created to write programs for the Newton platform.[1] It is heavily influenced by the Self programming language, but modified to be more suited to needs of mobile and embedded devices.[2]
History
On August 3, 1993, Apple unveiled the Apple Newton MessagePad. The device had 640 KB RAM, 4 MB ROM, and an 20 MHz ARM 610 microprocessor.
The main intention behind Newton project, was to develop a device capable of replacing a computer while being portable. With limited battery and memory, the developers were looking for programming language capable of meeting these challenges.
The developers looked at the C++ programming language but realized that it lacked flexibility. They started focusing on prototype based languages and were impressed with Smalltalk and Self.[3] Concurrently Apple was developing another dynamic programming language called Dylan, which was a strong candidate for the Newton platform.[4]
However, both Self and Dylan were dropped out of consideration, as they were both in nascent stage for proper integration.
Instead, a team headed by Walter R. Smith developed a new language called NewtonScript. It was influenced by dynamic language like Smalltalk and prototype model based like Self.[3]
Features
Although NewtonScript was heavily influenced by Self, there were some differences in both the languages.
Differences arose due to three perceived problems with Self.
- One is that the typical Self snapshot requires 32 MB of RAM to run in, whereas the Newton platform was designed to use only 128 KB for the operating system. This required some serious paring down of the engine to make it fit and still have room for applications.
- Another issue was performance. Since the language would be used for the entire system, as opposed to just running on an existing operating system, it needed to run as fast as possible.
- Finally, the inheritance system in the normal Self engine had a single parent object,[5] whereas GUIs typically have two — one for the objects and another for the GUI layout that is typically handled via the addition of a slot in some sort of GUI-hierarchy object (like View).
The syntax was also modified to allow a more text-based programming style, as opposed to Self's widespread use of a GUI environment for programming. This allowed Newton programs to be developed on a computer running the Toolkit, where the programs would be compiled and then downloaded to a Newton device for running.
One of the advantages of NewtonScript's prototype based inheritance was reduced memory usage, a key consideration in the 128 KB Newton. The prototype of a GUI object could actually be stored in ROM, so there was no need to copy default data or functions into working memory.
Unlike class-based languages, where creation of an object involves memory being allocated to all of its attributes, NewtonScripts' use of prototype inheritance allowed it to allocated memory to few fields like _proto and _parent instead of creating whole new object. Here, _proto and _parent signifies whether the object is using prototype or parent inheritance.[6]
An example to illustrate above concept, a developer might create a new button instance. If the button uses the default font, accessing its font "slot" (i.e., property or member variable) will return a value that is actually stored in ROM; the button instance in RAM does not have a value in its own font slot, so the prototype inheritance chain is followed until a value is found. If the developer then changes the button's font, setting its font slot to a new value will override the prototype; this override value is stored in RAM. NewtonScript's "differential inheritance" therefore made efficient use of the Newton's expensive flash RAM by storing the bulk of the default data and code in the PDA's cheaper and much larger ROM.
Important terms
Views: They are objects created by Newton View System, which are created on run-time to render views.
Template: It is a blueprint from which views are created.
Protos: They can be blueprint for a template or a view, and are elements of NewtonScript code libraries.
Frame and Slot: Frame is a dynamic collection of slots, and one element of frame is called as a slot. A slot is made up of name and value. The value can be of any type. It is worthwhile to note that all objects in NewtonScript are frames.[7]
Soup and Entry: It is a related collection of frames/ data. Entry is an individual frame in a soup.
Frame Heap: RAM allocated dynamically by NewtonScript.
Base View: It is the main view of application, consisting of all the variables and methods used in the application.
Advantages and disadvantages
- Advantages
- NewtonScript is a dynamic prototype based programming language, which uses differential inheritance. This means that it is very effective in using memory space. Being dynamic, it is easy to modify objects, type checking, etc. at run time, giving great flexibility for developers.
- Objects created can be stored in permanent memory like flash card or internal memory. The RAM is used only for storing attributes whose values change during runtime. This reduces memory consumption.
- Writing interfaces for GUI applications can be implemented effectively using the prototype model, since we can directly write an object for a GUI control rather than creating a class and instantiating it.
- Garbage collection is carried automatically by the system. This helped the developers to focus more on application development rather than worrying about memory management. Garbage collection also helped in mitigating problem of dangling pointers where a pointer erroneously points to a memory location that was deallocated.[6]
- Disadvantages
- Since NewtonScript code was written on one platform and run on another, it was practically impossible to debug.[2] Better debugging code in the Newton engine would have helped offset this problem to some degree, but the limited memory made this difficult. Instead the developer would get a vague indication along with an error code, without any ability to match it to lines in the original code.
- Another disadvantage is that, dynamic variable reduces the speed of operation since simple pointer dereference cannot be used as in statically typed like C++ and Java.
Influences
With the cancellation of the Newton project by Apple in 1998,[8] all further mainstream developments on NewtonScript were stopped. However, the features used in NewtonScript would continue to inspire other programming models and languages.
The prototype-based object model of Self and NewtonScript was used in JavaScript, the most popular and visible language to use the concept so far.
NewtonScript is also one of the conceptual ancestors (together with Smalltalk, Self, Act1, Lisp and Lua) of a general-purpose programming language called Io[9] which implements the same differential inheritance model, which was used in NewtonScript to conserve memory.
See also
References
- ↑ Smith, W. R. (1994-02-01). "The Newton application architecture". Proceedings of COMPCON '94. 156–161. doi:10.1109/CMPCON.1994.282931. ISBN 978-0-8186-5380-3.
- ↑ 2.0 2.1 Schödl, Arno (2004-10-10). "The NewtonScript Programming Language". http://www.cc.gatech.edu/~schoedl/projects/NewtonScript/.
- ↑ 3.0 3.1 Smith, Walter R. (1995-01-01). "Using a prototype-based language for user interface". Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applications - OOPSLA '95. New York, NY, USA: ACM. pp. 61–72. doi:10.1145/217838.217844. ISBN 978-0897917032.
- ↑ "Dylan: An Object Oriented Dynamic Language". http://www.cise.ufl.edu/~jnw/Marlais/OODL.html.
- ↑ Chambers, C.; Ungar, D.; Lee, E. (1989-01-01). "An efficient implementation of SELF a dynamically-typed object-oriented language based on prototypes". Conference proceedings on Object-oriented programming systems, languages and applications - OOPSLA '89. New York, NY, USA: ACM. pp. 49–70. doi:10.1145/74877.74884. ISBN 978-0897913331.
- ↑ 6.0 6.1 "The NewtonScript Programming Language". 1996. Archived from the original on 2015-01-24. https://web.archive.org/web/20150124193723/https://manuals.info.apple.com/MANUALS/1000/MA1508/en_US/NewtonScriptProgramLanguage.PDF.
- ↑ McKeehan, Julie; Rhodes, Neil (1994). Programming for the Newton®: Software Development with NewtonscriptTM. 955 Massachusetts Avenue, Cambridge, Massachusetts 02139: AP Professional. ISBN 978-0-12-484800-9.
- ↑ "Apple cancels Newton". 1998-02-28. http://windowsitpro.com/windows-server/apple-cancels-newton.
- ↑ "io guide". http://iolanguage.org/guide/guide.html.
External links
- SELF and the Origins of NewtonScript , by Walter Smith, 1994.
- Using a Prototype-based Language for User Interface: The Newton Project’s Experience (PDF), by Walter Smith, 1995.
- Class-based NewtonScript Programming by Walter Smith, 1993.
- Additional Newton-related papers by Walter Smith.
- The NewtonScript Programming Language (archive.org cache; original link dead as of 10/15/04.)
- NEWT/0 A portable NewtonScript compiler/interpreter
- NewtDevEnv, a NewtonScript development environment that enables development to be carried out directly on the Newton by Steve Weyer.
- DyneTK, a NewtonScript development environment that replaces the original Newton ToolKit (NTK); works on MS Windows and Mac OS X by Matthias Melcher.
 |  |
