From: David B. <dba...@ed...> - 2007-03-05 15:11:26
|
----- Original Message ----- From: "Jan Waclawek" <we...@ef...> To: "Development chatter about sdcc" <sdc...@li...> Sent: Saturday, March 03, 2007 2:32 AM Subject: Re: [sdcc-devel] Dissection of a compiler > David, > > That was me who started and attempted this sort of documentation. > > Meantime, I also attempted to set up for compiling the sources, even > started > to play with linux because of it, and failed repeatedly. This is simply > beyond my rather limited capabilities of a small embedded programmer... I certainly know the feeling. > However, I still have hope that I might be able to figure out whereabouts > of > the compiler simply by reading the sources. I plan to continue on the > documentation, when I find time and energy to do it. Don't feel too obligated. Free software is all about fun =). Just reading the sources without getting them running might be kinda rough on you unless you have some amazing source code analysis tools. Anyway, you did a great job nosing out some information. I think some of the problem is that the developers who really understand the guts of SDCC don't remember what they had trouble understanding to begin with. Of course, they're also busy enough with actually fixing bugs and now with setting up the build environment. I just hope we're not annoying them with the questions and discussion when they're trying to get other work done (are we?). > Meantime, any contribution is welcome... :-) > > Jan Waclawek > > > > > David Barnett wrote: > >> On another note, the "internals and porting" seems to have stagnated. If > we >> could keep adding to it here and there when we have a free moment, it > would >> go a long way helping people like me to dive in (I say "we", but I don't >> know any more useful information to add yet, and I suspect some of what I >> did add isn't accurate). |