Maarten, Actually, I sent this mail to the -devel maillist first, but it requires confirmation which I think is far from being flexible enough... Also, the -devel maillist is full of buglist notice, it's hard to find anything reasonable there, especially considering the rather broken interface of it (any useable interface or bulk archive available? - this is maybe question #0). Maybe a new maillist could be set up for this purpose? Or shall I move this to some other forum, or perhaps a wiki?
Anyway, my question(s) #1. >From the start. Sdccman.pdf in the "anatomy" chapter, first section, says, that the first step in compilation is parsing. The source of that, if I understand it correctly, is sdcc/src/src/SDCC.y, which is "compiled" using bison. It is mentioned also, that there are device-dependent parts even in this step. Where are sources for these specific parts located? It is said there, that the result of parsing is AST. How does it look like (any description?) and where is it located (in memory/in any file?) A final question: where are the macros expanded? Jan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
