Back to the PIC coding today. I have decided on how I will structure the code. This can be a pain given the capabilities of the language. Since I am using a version of Basic, then things are not as good as they could be. Also since I am using a CPU that would be more at home in a washing machine than a sophisticated device there are limitation as to what I can do. <\/p>\n
So I need to use an interrupt routine to do some of the things that I would normally do in the foreground. That is, Instead of checking if it has been 100 mSec since the last call to a function, I set a timer, and force the timer to run no matter what every 100 mSec. I like to be more cooperative than that, but this is not always possible – as I have just explained. I hope to get a large percentage of this code written today. I am sure that there will be many many issues to solve, but… Well there is a saying I like….
The first 90% of the code takes 90% of the time, and the last 10% of the code takes the other 90% of the time<\/i><\/p>\n
I know, the numbers do not add up. But coding never takes the time you expect. Things always happen… Always. <\/p>\n
I saw this on a Mailing List…
Ability to Fly:
Hurling yourself towards the ground, and missing.<\/p>\n
Engineers that Contribute to flying:
Both optimists and pessimists contribute to the society. The optimist invents the aeroplane, the pessimist the parachute<\/p>\n
Pilots that are Flying:
Those who know their limitations, and respect the green side of the grass… <\/i><\/p>\n","protected":false},"excerpt":{"rendered":"
Back to the PIC coding today. I have decided on how I will structure the code. This can be a pain given the capabilities of the language. Since I am using a version of Basic, then things are not as …<\/p>\n