piclist 2008\07\22\144502a >
Thread: What to do about compiler bug and source code?
face BY : sergio masci email (remove spam text)

On Tue, 22 Jul 2008, William Couture wrote:

{Quote hidden}

Strip out as much source code as possible such that the compiler still
produces the bug.

Start off with a copy of the project. Systematically delete the contents
of functions which are unrelated to the function where you are
experiencing the problem (leaving just the empty function). Keep doing
this until the compiler starts behaving, then undo until the compiler
starts misbehaving again. Make a note of which functions are vital to
the bug and then try again with functions you havent touched yet.

You will end up with some functions and globals which are not referenced
anywhere. try removing them completely, a few at a time until the compiler
starts behaving itself again, then undo the changes until the compiler
starts misbehaving again. you should be able to drastically reduce the
code necessary to reliably reproduce bug.

Sergio Masci
<Pine.LNX.4.61.0807222141200.23366@yoda.srts.co.uk> 7bit

In reply to: <8ffe5b0c0807221045y2108b155r792421dd1261abe0@mail.gmail.com>
See also: www.piclist.com/techref/index.htm?key=what+about+compiler
Reply You must be a member of the piclist mailing list (not only a www.piclist.com member) to post to the piclist. This form requires JavaScript and a browser/email client that can handle form mailto: posts.
Subject (change) What to do about compiler bug and source code?

month overview.

new search...