Joep Suijs wrote:
And about case 5...
(calculations with multibyte variables with 16f73/74)
IMO a warning is not enough. The use of large math in small programs will work okay, but larger programs fail silently in some cases. In other words: instable behavior. I suggest that, in addition to the warning, we remove the definition of _pic_accum for 16f73/74. This way programs that use large math won't compile and guarantee stable behavior. This is of course at a cost: small programs could have used large math, but can't now. But this is cheap compared to the hassle of instable code.
When _pic_accum is only used for calculations with multi-byte variables then this might be a good solution.
BTW: The warning (with _warn) causes a non-zero returncode by the compiler. This is somewhat annoying, since the compile is otherwise OK. Is there a method of generating a log message with zero returncode?
Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
