Dear Marc, For a layperson to read through the compiler's sources (i.e. gsc/*.scm) as to get a general understanding of its internal workings, would you suggest any particular reading order, be it sequential or parallell? Also, would there be any contextual understanding that would be particularly important to have - such as for instance, structural qualities to the code that, for a reader to make sense of them, he must have already a particular frame of reference? (to avoid 'saving an hour theory by spending a month in the lab'.) At its 41klocs, it would be feasible for a user to read all of it and actually get to a pretty good understanding! That appears to me like a worthy cause. Thanks! Mikael