Partically complete Lexer+Symbol table+Parser for the autoit language

[twitchyliquid64]

The title/subtitle says it all.

WARNING!

This code was originally a personal proof of concept. It is neither complete nor fully compliant with the autoit language. (For example, several keywords such as IN or ENUM are not supported) Do NOT expect anything amazing nor inspirational!

I am meerly posting this in the hope that some may find this code useful.

https://bitbucket.org/hyperzap/bleb-autoit-compiler/src

All the compiler code is in /compiler.au3 and /engine/. /Build/ is what is generated by the compiler.

I have tried to break things up as much as possible - you will find a lot of comments everywhere, particually in large blocks.

A good place to start is /compiler.au3 and /engine/general.au3.

I hope someone finds this useful.

Regards,

Twitchyliquid64.

Edited April 13, 2013 by twitchyliquid64

[Shaggi]

Reading through it all know... This is sexy. Keep going on, i might help, too

e: How are you going to handle internal autoit function commands? ie. consolewrite and such - if you ever planned to go so far?

Edited August 24, 2011 by Shaggi

[twitchyliquid64]

Reading through it all know... This is sexy. Keep going on, i might help, too

e: How are you going to handle internal autoit function commands? ie. consolewrite and such - if you ever planned to go so far?

the original idea was that there would be some kind of modular plugin system which would be used when a function call was used, and the code would be emitted from that.

obviously, someone needs to rewrite all the builtin functions in c.

[Shaggi]

the original idea was that there would be some kind of modular plugin system which would be used when a function call was used, and the code would be emitted from that.

obviously, someone needs to rewrite all the builtin functions in c.

Well the easy way would be to use autoitx dll linking..

But rewriting the functions shouldn't be that hard, seiing as a lot is just wrappers and a lot of the source can be retrieved from old au3 source and ahk.

Have you thought of moving to c++? tcc kinda sucks

[twitchyliquid64]

moving to c++ involves using a c++ compiler for final code generation. there are no c++ compilers that are sufficiently lightweight for my purposes.

tcc does an excellent job of converting c code into instructions with only the most essential optimisations, something i need to get enough control of the build process.

autoitx would be amazing...if it supported all the functions. it supports the hard automating functions though, so it will be incorporated.

[twitchyliquid64]

moving to c++ involves using a c++ compiler for final code generation. there are no c++ compilers that are sufficiently lightweight for my purposes.

tcc does an excellent job of converting c code into instructions with only the most essential optimisations, something i need to get enough control of the build process.

autoitx would be amazing...if it supported all the functions. it supports the hard automating functions though, so it will be incorporated.

[Shaggi]

moving to c++ involves using a c++ compiler for final code generation. there are no c++ compilers that are sufficiently lightweight for my purposes.

tcc does an excellent job of converting c code into instructions with only the most essential optimisations, something i need to get enough control of the build process.

autoitx would be amazing...if it supported all the functions. it supports the hard automating functions though, so it will be incorporated.

What's left is I/O, math, type conversion and little else that every language supports and therefore wont be hard to implement. Only thing thats missing is the GUI system Edited August 26, 2011 by Shaggi