OSDev.org

Since there seems to be a lot of interest in systems programming in languages other than C or C++ in the OS forum I thought I'd start up a thread for one of the three most common ideas: an object-oriented language similar to SmallTalk (the others, a member of the Lisp family and a Basic derivative, will have separate threads). I have given this putative language the tenative name 'Obscene'.

To start things off, we need to know what people want in the language, and to consider which of those 'wish list items' is practical for the sort of low-level language we want. Does anyone have anything to start with?

Does anyone have any ideas they wish to borrow from other OO languages such as Self, Java, Eiffel, or Sather? Keep in mind that only a very minimal subset will be possible, and that there will, of necessity, be some considerable changes and additions; In effect, this will be a new dialect in and of itself. If anyone can find any reference material on Smalltalk, it could prove useful as a starting point.

SmallTalk is still alive and well. Check it out. I love the quotes section. XD

What is your take on forth? Im in the process of designing a new language thats similar to forth, and small talk.

what is a language ?
.. it is some form of protocol uppon which communication is carried
as far as computers go, a way to talk to them
to give them instructions on how to do things
cause ai machine learning sucks these days
a physical limit of what a flat processor can do
is what can we teach him
we must be able to describe every tiny detail
at the same time, not losing focus from our original target
our programs must be modular
so as not to have to write them from scratch each time
but reuse common parts
elegant sollutions are a programmer's job
little chips are merely for proof testing
and we need to be able to express ourselves
from near signal analog-to-digital encoding
to virtual reality systems simulation
what is requested is a language that will serve you well
not because it is compiled (optimization is not an issue here)
or cause of its extensive libraries (these will develop in time)
rather due to the flexibility of its syntax
ideas are important enough not to be blocked by monolithic forms
an evolving language
one that will let you define your own abstractions
your very own dialect
you are not talking to a machine here
it is your fellow co worker who will be reading your code
who will try to shape it as to take a new form
and who does care if you are right or wrong ?
things change, and code should change with them
what can be computed is an old puzzle
what you can express is a much more difficult one

OK, let's start with basic grammar. Not deviating too far from Smaltalk, we would have a method syntax something like:
Hopefully that will do as a start. C&CW.