We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I rarely ask questions on this forum, but since I couldn't [easily] find it in the help-files, or on-line, I'm asking you guys.
I usually (like never) don't use the 'reentrant' pragma, but I think I may have to do that with a particular routine.
BUT I can't find the key-word that declares a function as reentrant. Am I missing something? Is there one for Keil's IDE tools? If so, what is its form? Can I get a link to the 'official' use of it?
Thanks in advance, and I need it asap because I need to pass this class and I don't want to really learn how to do this 'embedded' stuff anyway but the teacher keeps hounding me.
--Cpt. Vince Foster 2nd Cannon Place Fort Marcy Park, VA
Yes, in the Aero/Mil industry things get well defined and 'new' features are rarely added without a big deal being made. Yet still those little features added still occur... and often.
As a boss of mine said (known as Miller's Law):
"Resist All Temptation to Increase Expectation"
Which meant not to imply to the customer that you can do this or that just because you know you can... they'll just expect it for free.
In the R&D missile business, we're doing stuff that we don't know for sure if it will work even deep into the design cycles. That "MRM" (XM1111) project was a killer because we (I) had to fit 10 pounds of circuitry into a 1 ounce PWA. It was 'theoretically possible' but there are real-world aspects that were high-risk. But the MRM worked and we (not just me) made it work PERFECTLY. Excalibur (XM982) was similarly hard.
Jobs that have ever-changing criteria are nightmares to deal with. So the more practical solution (in low-volume cases) is to over design it to be capable of expansion if needed. Then when that feedback comes in on how it is used, you can do a cost reduction and re design it for those high-volume jobs.
I just want you to know, that 'sexy' R&D missiles and what you do Per are really the same thing. The only differences could be the funding and the amount of paperwork and qualifications the widgets need to go through. (Assuming that you also do that real engineering work up front, which I think you do indeed do).
And don't worry about 'rambling' because I'm the worst offender of it.