Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualL. Spiro

Posted 14 January 2013 - 06:16 AM

That’s not been my experience (to slicer4ever).

 

Doing a clean build removes .OBJ files from different versions of compilers and this can have a profound effect on the stability of the resulting .EXE.

I even have the same compiler on both my Windows XP and Windows 7 installs, same service packs, etc.  But when I switch between Windows XP and Windows 7 I really have to do a clean or I am guaranteed to get segment faults and other strange behavior.

Many times in the most isolated areas I have been able to prove the code was correct.  A clean rebuild became part of my routine and I no longer suspect any underlying issues with the code.

 

As for the original poster, if you work with your code between different machines, save yourself some hassle and get into the habit of cleaning each time you copy the code and project to a new machine.  Once again, for me, failure to do so always results in some kind of crazy run-time crash that makes no sense.

 

 

L. Spiro


#1L. Spiro

Posted 14 January 2013 - 06:14 AM

That’s not been my experience (to slicer4ever).

 

Doing a clean build removes .OBJ files from different versions of compilers and this can have a profound effect on the stability of the resulting .EXE.

I even have the same compiler on both my Windows XP and Windows 7 installs, same service packs, etc.  But when I switch between Windows XP and Windows 7 I really have to do a clean or I am guaranteed to get segment faults and other strange behavior.

Many times in the most isolated areas I have been able to prove the code was correct.  A clean rebuild became part of my routine and I no longer suspect any underlying issues with the code.

 

 

L. Spiro


PARTNERS