Jaime Oliver wrote:
Well in this particular object I have two for loops in the RGB process:
int i, n; for ( i=0; i<3; i++) { post("i=%d", i); for (n=0; n<3; n++) { post("n=%d", n); // other things } }
when compiled in osx it sometimes posts the inner loop, but sometimes it doesn't depending on whether I have those 'other things' commented or not, it could even be two posts that are not interfering or reinitializing the for variables (i or n), so that leads me to assume (also based on the fact that it isn't giving me the correct results at all), that the inner loop is not being done.
thanks for the clearup. i suspect it is a bug in either your code or the compiler/optimizer. does it help if you do not use pd's built-in console but instead print to stderr (with the "-stderr" flag)? stderr is way faster than pd's console.
do a "make clean" (or even "make distclean"; alternatively try to delete all the "*.o" and "*.d" files in all the subdirectories) before you build. you seem to have leftovers from old builds. (i was never able to really figure out what is going wrong here)Thanks, I'll try those things and report back. Will this clean all my other GEM objects as well?
yes it will. you have to rebuild everything then. if you don't want that, you can also cd into the Pixes directory and do a "make distclean" there, then you will only have to rebuild the entire Pixes-stuff.
fgmasdr IOhannes