Jan, see below, please.
regards, Richard Erlacher ----- Original Message ----- From: "Jan Waclawek" <[EMAIL PROTECTED]> To: <sdcc-user@lists.sourceforge.net> Sent: Friday, August 29, 2008 2:52 AM Subject: [Sdcc-user] Quickstart document,was: Virus in SDCC-2.8.0-setup.exe - MD5 etc tutorial > Richard, > >> [...] and I'd be happy to help generate a more > user-manual-for-Windows-Users sort of document >> that assumes nothing about one's knowledge of LINUX or *NIX, >> and targets those who would prefer to utilize this tool set from Windows > rather than having to move to LINUX, >> if only I could find out how to use the tool set in the first place. > > OK. Ask. > I have a 'C' program, which I hope will work, on paper in my hand ... There's a computer running Windows on the desk in front of me. I want to compile this program for introduction by whatever means might be available into a system based on one of the target MCU's supported by SDCC. What's my first step? ... then what ... ? > > For those developers here who knows the ins and outs of SDCC very well is > hard to imagine what should be the content of a "quickstart" document. > "Quickstart" is not how I'd describe a User Guide. Maybe you're onto something, Jan ... maybe a "QuickStart" is what's called for as a first step. > > And, please note, that regardless of whether there is an up-front > specification for a software or not, the user documentation may be very > different from this specification or any other document a developer is > likely to write, if it has to be of any use for a real user; plus that > there > may be several "levels" of users (beginner, advanced user, > administrator...) > Yes, I know ... that ship has sailed ... Since the program already exists, there's no way to "un-create" it and go back to what, perhaps, should have been done before it was coded. > >> I'd even be interested in helping with the generation of a simulator for > the various MCU's, starting of course, >> with the 805x's as those are the ones of current interest, > > There _is_ a '51 simulator which comes with SDCC, but it is rather > cumbersome to use and has a command-line interface only (read: command > line, > no text-screen). It is not intended to be used by human, rather, in an > automated simulation setup (primarily for the regression testing after a > new > build of SDCC). > I've looked for it, but haven't found one that operates as one might expect. Perhaps its doc's need clarification. Are there any? I recall reading something about a simulator and a link to a website that seemingly no longer works. I always found simulators quite straightforward. The difficult part is getting a complete characterization of whatever's to be simulated. Approximations don't make a simulator work well. In this context, the "trick" is to predefine the environment within which the simulator has to function. Handwaves don't help, either. Some things have to be clearly defined, at least in terms of inputs, outputs, and processes. > > Jan Waclawek > ------------------------------------------------------------------------- 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
