Hi Vasile, 2010/5/23 vasile surducan <[email protected]>: > Everytime I'm starting writing software (I'm not doing this every day) I > found unusual problems, the sort of errors you're never talking about here. We seem to discuss this only if two people run into the same issue (error). In this era, most work on this list is done in 'single user mode'...
> I've used the words errors instead of bugs because I've seen Kyle is very > sensitive to this word... Sometimes I find it difficult too to determine if I found a compiler bug (something the compiler does not do like it should), a libarary bug, a bug in my software or one in my mind - something that works not like I expect because my expectations are wrong. The 5 'bugreports' I issued on the beta-compiler on average represent a half day of bug-tracking each, so you are not the only one. Well... there is a new beta so let's test it and see wich issues are solved... > and because probably are only from my fault or > weird use of the programming language). Weird use or wrong expectations. E.g. promotion rules are sometimes tricky too, but this will be the case in other languages too. And I haven't tried other pic16 compilers, but hear they have bugs too and JAL is rated as the most relaiable option. But you should avoid the beta version... I guess the only way to avoid compiler bugs is program in assembler. Assemblling is straight-forward, so an assembler bug that is producing wrong code is less likely. Joep -- 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.
