|[2 earlier articles]|
|Re: Implementing classes email@example.com (Julian Stecklina) (2005-08-21)|
|Re: Implementing classes firstname.lastname@example.org (Nathan Moore) (2005-08-31)|
|Implementing classes email@example.com (Jatin Bhateja, Noida) (2005-09-02)|
|Re: Implementing classes Juergen.Kahrs@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2005-09-04)|
|Re: Implementing classes firstname.lastname@example.org (2005-09-10)|
|Re: Implementing classes darnottJUNK@rogers.com (Doug Arnott) (2005-09-11)|
|Re: Implementing classes email@example.com (Oliver Bandel) (2005-09-11)|
|Re: Implementing classes firstname.lastname@example.org (2005-09-14)|
|Re: Implementing classes email@example.com (Julian Stecklina) (2005-09-14)|
|From:||Oliver Bandel <firstname.lastname@example.org>|
|Date:||11 Sep 2005 11:13:06 -0400|
|Organization:||Individual Network Berlin e.V.|
|Posted-Date:||11 Sep 2005 11:13:06 EDT|
Kevin Szabo wrote:
> If you are creating a 'new' language you should look hard at the goals
> you are trying to achieve. If it is to just learn about the process,
> then please have a look at 'little smalltalk' by Timothy Bud. It is a
> *small* implementation of smalltalk, a pure OO language.
> If you want to see how to turn C into an OO language (but not C++) you
> may want to look at Brad Cox's book:
> Object-oriented programming: An evolutionary approach by Brad J Cox
> Although an older book, it is an excellent introduction because it
> doesn't assume the reader has OO experience. It tells you about ISA
> and KINDOF and SUBCLASS/SUPERCLASS; all good stuff.
> And finally, if you are trying to contribute to the state of the art,
> by creating a new language to solve interesting problems, you should
> read all that you can. Smalltalk the language and implementation.
> The C++ book by Stroustrup, the JAVA whitepapers. RUBY. Python. Try
> programming in the languages.
Isn't LISP's OO-System the most powerfull?
And what's about labguages which have functional Objects,
for example OCaml?!
The Laban Scale Document-Generator:
Return to the
Search the comp.compilers archives again.