Re: [Oopic-compiler-devel] OOPic Compiler
Status: Planning
Brought to you by:
ndurant
From: Andrew P. <wa...@ic...> - 2004-10-19 05:10:26
|
At 12:57 AM 19/10/2004 +0100, Neil Durant wrote: >Hiya folks! > >Long time no traffic on this list! Just thought I'd post something to see >if everyone is still interested in going ahead with this project? I thought you'd have it done by now! >After the discussion about using Python as an implementation language for >the OOPic compiler, I bought a book on Python and have spent the last >couple of months learning it, and I have to say, it's an ideal language for >this kind of project. I kept thinking as I read parts of the book, "That >would be excellent for writing a parser" or suchlike. And the >platform-independent aspect comes for free. > >So now, having finished the book, I'm keen to launch into some >development, and I really think we should use Python! I don't think I'll be doing my part in Python, but that doesn't mean others can't do their modules that way. >Thoughts? Let's get this project moving! I've made available my initial efforts at a .oex file disassembler; it's still fairly rough, but hopefully it will inspire y'all. It's at: <http://home.ica.net/~phoenix/wap/OOPic/OEX-VIEW.ZIP> The .c file is the original OOPic source code and the .txt file is the disassembler output of the .oex file. The .xlat file has to be built by the human in charge... I'd be interested in knowing how the disassembler handles your own .oex files. ...Andy |