should #include be read as a comment or not?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use i.e. #include policies/linux/monitoring in your policy 
(because you wanna add it later, not now)

What is the expected output? What do you see instead?
ignore the line and not try to parse the include file

What version of the product are you using? On what operating system?
svn version 

Please provide any additional information below.
this may not be an issue at all. I don't know the syntax well enough yet, 
opening the issue because i won't remember once I got used to working around it 
:)

Original issue reported on code.google.com by florian....@gmail.com on 6 Jun 2011 at 8:28

[GoogleCodeExporter]

re-reading the r112 release announcement it has become clear that the hash is, 
indeed, not a comment symbol :>

Original comment by florian....@gmail.com on 6 Jun 2011 at 8:30

[GoogleCodeExporter]

Yeah, this is a bit confusing I suppose.  I went with "#include" for 
familiarity with certain programming languages but it may not have been the 
ideal choice.  

Original comment by watson@google.com on 13 Jul 2011 at 11:02

• Changed state: WontFix

[GoogleCodeExporter]

Yeah, this is a bit confusing I suppose.  I went with "#include" for 
familiarity with certain programming languages but it may not have been the 
ideal choice.  

Original comment by watson@google.com on 13 Jul 2011 at 11:02