> Are you generating the source code as well as the documentation from a
> pseudo code? Or maybe I am completely misunderstanding the way mkt works?

Mostly the C or assembler source is in a string constant in the Python 
source. In some cases it is tweaked a little (for instance with the 
actual pins a HD44780 LCD is connected to). But there are cases where 
the C or assembler source is generated by Python code. Examples are the 
fixed-GPIO-pin-set and -clear macro's, and the interface to the chip's 
peripheral registers.

The documentation is in nearly all cases a string constant, which is (as 
far as possible) near the string constant for the code (or at least for 
the C header).

The library-generating code is a class tree with the common parts in the 
base class, and the more specialized parts in derived classes. The 
documentation is in that same structure, with a hack that makes 
specifying a documentation function in a derived class adding to the 
original instead of replacing it.

I am not sure that last part is very clear. But you could try to read 
mkt.py, it is only ~ 8500 lines ;)

-- 

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist