Dave, I really wish you'd quit imposing your agenda on the discussion. This has nothing to do with the tools vs. workman issue, but, rather, has to do with the fact that just because the compiler doesn't produce the code the coder wanted, doesn't mean that there's a bug in the compiler.
Further, the fact that a programmer, on occasion, abuses the language, doesn't mean that he's incompetent. It simply means he's committed an error. That's not grounds for banishment from the programmer community. The discussion, with the exception of the "wild-hares" you've occasionally chosen to pursue, is about the widely agreed-upon notion that the documentation is in dire need of repair/rework. There's nothing that can be done about the fact that objective documentation wasn't generated in advance of the coding. There's nothing that can be done about the fact that full and complete documentation was not provided at the outset. However, there IS something that can be done to remedy the current state of the doc's and rather than suffering on with it, along with everyone else who has yet to learn the ins and outs of SDCC, I'm willing to help do something about the doc's. It has nothing to do with whether or not I presently need to compile some 'C' code for this MCU or that. It simply has to do with finding a basis for making corrections, revisions, updates, -- call them what you will -- to the existing doc's. Now, I asked you a question several rounds ago ... Given what appears to be an acceptable ASM file, how would I use the assemblers, in this case the one for 805x-types, to generate a hex and an OMF file using the SDCC tools? What are the steps, in sequence, that I have to go through, under Windows, at a DOS prompt, from within a directory containing both the assembler and the source file, in order to get from my plain-text ASM file to the desired output? regards, Richard Erlacher ----- Original Message ----- From: "Dave McGuire" <[EMAIL PROTECTED]> To: <sdcc-user@lists.sourceforge.net> Sent: Saturday, September 06, 2008 11:12 AM Subject: Re: [Sdcc-user] documentation & open source generally > On Sep 6, 2008, at 12:30 PM, Richard Erlacher wrote: >> However, 'C' is notorious for compiling successfully, yet not at >> all doing >> what was intended, due to some coding or design error. > > I apologize for responding to a part of the conversation in which > I was not involved, but I could not let this pass. > > This has precisely ZERO to do with C, and everything to do with > incompetent programmers. Don't blame the tool for the incompetent > person who wields it. > > I make huge messes whenever I pick up a hammer. Does that mean my > particular brand of hammer is notorious for making messes? No...it > means I should either develop the skills required to use the hammer > properly, or find a line of work that doesn't involve the use of > hammers. > > -Dave >> > > > -- > Dave McGuire > Port Charlotte, FL > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sdcc-user ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
