-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Mar 30, 2008 at 12:05:56PM +0200, Wouter van Ooijen wrote:
> > Compiler writing 'eh? Where do you end up doing that?
> 
> At home :)
> 
> But I have to admit that I have not done much in that area since the old 
> Jal (the new Jal is not my work).

Ahh, cool. I wrote a compiler for a made up C like language years ago as
a school project, it worked, but I haven't done anything along those
lines since.

I do have some half-baked thoughts to see if I can "compile" a limited
subset of Python into either PIC assembler directly or C, sutable for a
microprocessor. Basically I'd just take advantage of how simple the
Python virtual machine is and translate those opcodes rather than
actually parse Python. It might be a nice way to write behavioral code
that could be eailly run and written on a simulator on the compuer, and
then later downloaded to PIC-based nodes in hardware.

> Right now I am writing a documentation extractor/formatter, which is not 
> that different from a (simple) compiler. In Python. And it is for an ARM 
> project, not for PICs...

If you haven't already heard of it, look up Python docutils and
restructured text. I'm starting to use it for documentation in my Tuke
library.

- -- 
peter[:-1]@petertodd.org http://petertodd.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH73nX3bMhDbI9xWQRAoV0AJ0djPgKSbeRjqigR88vg14v+Ybm0wCfYH02
cU59I4zeeDn0wreKArJLZ+w=
=KRun
-----END PGP SIGNATURE-----
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist