[<<][staapl][>>][..]
Sat Oct 10 11:26:34 CEST 2009

Next

It's getting complicated.  Time for some design decisions.

* It seems that keeping a loop in reference form is the best approach
  for now: memoization and pre-fill are easy to generate if not a bit
  tedious.  Some abstraction will help here.

* For loop transformations I need to read [1] and reuse the
  representation.

* With the syntax in place, it should be possible to start making and
  parameterizing source transformation rules using higher level
  constructs.

I need a problem to drive this.  Simple straight-line code isn't so
interesting as it seems that problem is solved.

Today seems to be a low-key day, so I'm going to do the bookkeeping
routines: generation of C code from let* form.


[1] isbn://1558602860



[Reply][About]
[<<][staapl][>>][..]