Project Zonnon: Oberon for distributed programming in the large

Contains odors of: Oberon and Actor Model type (E, Erlang, etc.) languages.

The Concepts of Zonnon:

  • design support for ‘programming in the large’
  • a modern object model that supports concurrency: activities in objects replacing passive method calls
  • formalised interaction between activities (dialogs)
  • good for structured and OO programming styles for a wide range of applications … OS to Business
  • retain the simplicity of PASCAL, Modula-2, Oberon family of languages
  • support multi-processor and distributed systems
  • support inter-operation with other languages and their libraries
  • produce a .NET Compiler, IDE, Test Suite and concise Language Report (40 Pages)

Some things: Facets: Allowing objects to not be forced into one major role; Syntax based 'dialogs' govern concurrent interaction; Object level concurrency/threads; Statement level concurrency; 40 page language specification.

When I skim the slides and see the code and statements about the approach to concurrency, it looks to me off the cuff that it would just make deadlock even bigger and more hairy. :-}

states in stateless machine

Hi all!

I'm experimenting with constructing a programming language for artificial intelligence programming. I want it also to be enabled for regular application programming. Right now i have thought through the stateless part, meaning that I have a rough definition of underlying stateless machine.

In real world there are also constructs that require statefull machines to hold some knowledge, but I'd hate to extend current language definition with additional statefull stuff that complicates the language that is now so simple without it.

So, I'm wondering are there known methods or new ideas to describe states inside stateless machines?

Tx :)