> Yeah, pretty cool. :) But you're right, this is somewhat risky. In this
> particular case, then, where we wan't include a VCL completely, it may
> be better to either split up the VCL in parts that we /can/ use directly
> in the docs 

lets try this. unless it becomes too cumbersome. or risk to show a
couple of lines that are not strictly needed for the doc.

> or do a normal code block here instead.

i would only do that for a 2-3 line example. otherwise we have the
oposite risk of thinking the vcl is included in the doc and not
remembering to adapt the doc when changing some configuration...