[Audacity-devel] guidelines for experimental.h

[Roger D. <rb...@cs...>]

I'm wondering about experimental features and CVS:

Suppose I comment out a define:
/* #define EXPERIMENTAL_NOTE_TRACK */
and commit changes. Everyone's build should be happily unaffected. Now, 
I want to work on the experimental code, so I uncomment the define. If I 
then commit new changes, the uncommented define will go into the 
repository (bad). I could put the comments back, but I think this would 
appear to be a new version (also bad). I guess I could revert to the 
older version of experimental.h before the commit (good, but seems 
error-prone).

This is all assuming the use of the Visual C++ IDE. I could put defines 
in the project file, but that has the same problems as editing 
experimental.h. I gather most developers are using configure to specify 
configuration options locally. I didn't see a VC++ or Xcode project file 
solution in the Experimental.h section of the Wiki, and there was some 
discussion on a list, but it wasn't clear there was a conclusion.

Any recommendations?

Thanks,
Roger