Mon Aug 24 19:04:41 CEST 2009
Rant about reflection
PF isn't really so much about Forth. The name is a historical
accident.. PF is really about building a simple, safe, dynamically
typed language with linear memory management.
Let me rant a bit.
Forth is.. well.. Forth :) There isn't much to say about it, except
that it's a very nice machine model with a hacked-together text
interpreter that's really too reflective.
Over the last couple of years I've moved more into the direction of
less reflective code, mostly guided by the PLT Scheme approach to
domain specific languages. The attempt in Staapl to ``unroll'' the
very reflective nature of standard Forth stands as one of the pilars
of my approach to concatenative languages.
In general the pattern seems to be that using very reflective
languages leads to very simple language cores and a lot of expressive
freedom, but in turn makes it easier to write programs that are harder
In a static programming style you put the cleverness in the types and
other static constraints: something a compiler can check and proove
consistent. In a dynamic language the cleverness goes right into the
core of things: anything can be special-cased.
The main point being that when code bases grow it seems to be
beneficial to be able to bolt things down in a more static way: huge
code bases can't be kept in a human head so you need a machine to help
manage at least part of the consistency. Adding some static
properties seems to be the only way to do that effectively.
I'm currently right in the middle of these two paradigms: I realize
dynamic languages are essential for debugging and exploration, but
also that static structure is necessary to put more meaning into code
you write for "later" when it's meaning is no longer in your
short-term memory. The holy grail seems to be to find ways to combine
these two in a productive manner. Gradual typing seems to be the way