Hello PIC.ers,
..
>[4] Beep the Loud-speaker.  This is a routine that is similar to the
>Flash-a-LED routine, but the Wait-times are somewhat shorter :-)
>
>
>That's all there is to it ...  So, Divide your problem into their "atoms"
>(smallest, undividable parts), Write an "atom" & check if it works. Than
>move on to the next "atom"  If two "atoms" do something together write the
>"atom" that connects those two.  You can look at it like a Piramide :
>First place the lowest stones, Put a row of stones ontop of that one, and
>so on.  The last stone is the top of the piramide, and is the main-program
>loop.  The technique is called "bottom Up programming".
>
>Greetz,
>  Rudy Wieser
..
Aye, indeed,    indeed aye.
All my paying product seems to get made this way.
..
That's despite the rules which put it that we should practice
`top-down' programming.        i.e.
Devise the general plan of attack,
 then break it down into compartment-isable hunks, each capable of being
dealt with on it's own. Split that down further into individual repetitive
i/o calls, etc. right down to bare metal.
..
Maybe I'm a Neanderthal in this, but I find it well nigh impossible
to walk confidently up the `top-down'  s/w design staircase until
I'm (first) totally sure of the planks I'm standing on.
Those real low-level routines gotta be nailed down first.
..
comments?      ... come on now, I know you're out there !
..
Best regards,   John

..
email from John Sanderson at
JS Controls, PO Box 1887, Boksburg 1460, Rep. South Africa
Manufacturer & purveyor of laboratory force testing apparatus
and related products and services.
Tel/fax: Johannesburg 893 4154    Cellphone 082 453 4815