|
From: Craig R. <cr...@wo...> - 2002-04-30 14:51:26
|
Yeah, I was looked at this some more last night, figured the best way to go was to create a small program with cup embeded so I could use C's IO to look at what's going on. The API document is a little dated, nothing major, I'm trying to keep some notes as I go though so I can remember what needs to be updated. I was still having a few problems, can't figure out why cup_compile() seems to return a different binary in my program versus using the '-o' option from the cup built from CVS, thus causing the VM to say I have an "incorrect magic". I probably won't have much time to look at this the rest of this week either, but your inputs are helpful, I need to look at the compiler more closely if anything just to better understand how to use the debug info. Later, Craig ----- Original Message ----- From: "Keith Jackson" <ke...@cr...> To: "Cup-Dev List" <cup...@li...> Sent: Tuesday, April 30, 2002 8:10 AM Subject: [Cup-Dev] TODO list > Rather that try and use SourceForge Task tracking/assignment with such a > relatively small project, I've created the doc/TODO file. So, we can fiddle > around in there. As I've been going thru the code, trying to figure out what > I've finished and what I havn't, I started writing it up. There is still a > lot of compiler work before much VM work can be done. I believe the VM is a > good shell for now, as you said Craig. The compiler has a lot going for it, > but is still lacking in some major features outlined in the TODO. Anyway, > I'll see what I can do on some of that, or you can, etc. DUnno when I'll > have a lot of time, but I'll see what I can do. :) > > Let me know if ya have any questions, of course. > > > Keith > > > |