I don't remember anything other than what Michael R. said.

FWIW, I remember discussion about avoiding problems with the 
individual section headers being commented with the /* */ style.  In 
other words we settled on using the 'C' style comments to comment out 
unwanted code to avoid inadvertently ending a comment if using the C++ 
style.

I'm pretty sure there was a good reason for this type of commenting 
out, but I can't recall it right now. Chuck, do you remember the reason?

Patches would be great.

Some configuration files (e.g. turba/config/sources.php.dist) have 
some sections (e.g. localldap) that are disabled by commenting out 
every single line with a // .



It would be better to change the commenting of these section using C 
style comments /*  */ . The main reason is that when upgrading to a 
newer module version, it's easy to integrate your own changes (usually 
a few line) using the diff/patch commands.



E.g. if I uncomment all the lines of the localldap section and then I 
modify only the server line I can do a diff between the .php.dist and 
the .php version and I would have only three lines changed (the 
starting comment /* , the server line and the ending */ comment ). 
With the // style comment I get tens of changed lines, to manually 
review, before applying the .php.dist -> .php patch to the newer 
module version, since the skeleton config section may have been changed.



Thanks