John, et al
I am interested in what you think are the better approach alternatives
to handle complexity and size (etc), what criteria should apply and why
one ranks higher than another.
For example, should a language support both actors and be model driven?
Is a mix of type inference and
At Andrey's reference (2),there was an example that TCP/IP could be
modelled in less than a hundred LOC, whereas a C code version might be
more than an order of magnitude larger.
Is that model available?
Regards,
Gerry Jensen
02 9713 6004
Alan Kay wrote:
It used to be more clear. The main
Thanks Andrey,
i thought it might be useful to others (especially newbies who come here
first) to post a few other Ometa related URLs/posts, with yours
http://www.moserware.com/2008/04/towards-moores-law-software-part-3-of-3.html
http://www.tinlizzie.org/ometa/
You may find the concept of semantic slicing relevant:
http://www.cse.dmu.ac.uk/~mward/martin/papers/csmr2005-t.pdf
There is software at:
http://www.cse.dmu.ac.uk/~mward/fermat.html
One possible path to explore is to take GNU C etc intermediate
representation of source as the assembly language