You can just use hash (#) to comment a line in the configuration file.
To check the default or assigned values to various parameters based on your config file you can use the following
proc config=<config file name> ?
If you are on a unix/linux based system use backslash before the '?'
When I invoke Pro*C from within Visual Studio with the following pcscfg.cfg file
+# The commented lines below are in the original pcscfg.cfg file. They+
+# are commented out here in favor of command-line equivalents in the+
+# .vcproj file. See the properties on the .pc file for details+
+# include=%SRCHOME%/precomp/public+ define=(WIN32_LEAN_AND_MEAN)
I get the following response from Pro*C: System default option values taken from: d:\oracle_ic_sdk\win64\11.2\precomp\admin\pcscfg.cfg PCC-F-02041, CMD-LINE: Option does not exist: # include
It's a similar response if I comment out define directives and the like. Am I doing something wrong?
Edited by: biberdorf on Feb 22, 2012 1:53 PM
This is little strange, I just created a config file and I am able comment/uncomment any of the parameters in it with a hash(#) and able to see what values are in effect by running proc config=<config file name> \?
Can you try running proc from a command prompt.