I didn't mention that I almost exclusively use the QTP Expert View. This means that my comments are not in the Document column of the Keyword View. In the Keyword View they are shown as 'Comment' in the Item column.
Ah! you didn't say you wanted to document the comments. The solution I mentioned picks up the use of functions etc where you have used the @Documentation comment. So you could try that in your comment lines.
Or there is a VBScript comment puller on the net somewhere (can't remember exactly) and might be mentioned at The Scripting Guy site.
I have been using NaturalDocs for documenting QTP functions. Next week I will release a library that uses NaturalDocs for documentation. The function below should give you an idea of the formatting I use. The strings in <> are links to other functions and types documented in other parts of the library.
I am curious to know how you are using NaturalDocs and if your method differs from mine.
<font class="small">Code:</font><hr /><pre>
'Assert that the given expression is true
'bExpression - <Boolean> Expression to evaluate
'sEvent - <String> Event name for the log file
'sLogMessage - <String> Details for the log file
'<Boolean> True for pass, False for fail.
Public Function assertTrueAdv( bExpression, aOptions )
Set oOptions = GetOpts( ARRAY ( _
"sEvent", "AssertTrue", _
"sLogMessage", "Expected the given expression to return TRUE" _
assertTrueAdv = reportStatus(bExpression, oOptions("sEvent"), oOptions("sLogMessage"))