|
| | Re: motor repair
|
| hi Philippe, (...) Sorry, I don't know any translator , (with 1 Europe there should be one :-) but it's no problem for me to translate a few pages, tell me what pages you're interested in. Btw, Nice work, your laser target finder ! cheers, Stef (...) (21 years ago, 11-Jan-04, to lugnet.robotics.rcx, lugnet.technic, lugnet.robotics)
| | | | Re: Design by Contract (long post)
|
| Thanks, Tim. I haven't used the #x idiom myself - I like it. Your implementation with the boolean: (...) Will need an extra level of parenthesis surrounding the bool so that its declaration scope is made local. You can certainly go to town with this (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx, FTX)
| | | | Re: Design by Contract (long post)
|
| (...) For more fun with asserts: See if your compiler supports the FILE and LINE macros (or something equivilant). #ifdef NDEBUG #define assert(x) ((void)0) #else #define assert(x) if (x) else assertfail(FILE,LINE); #endif your assert_fail function (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx, FTX)
| | | | Re: Implementation of Installable Timers
|
| Iain McInnes wrote: [snip] (...) Great idea! (...) In your implementation, would it be possible for the client task to be killed (in the case of a run-away task)... causing the struct to be deallocated... while the struct is still in the linked (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| | | | Re: Design by Contract (long post)
|
| (...) I agree it seems to be the wrong way round. That's the standard implementation. NDEBUG seems to stand for "No debug". One advantage of making it negative, is that you get the assert()s if you don't do anything (ie dont define NDEBUG). BTW, (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
| |