We generally try to do this (include info about the return values and params) in the member description as much as possible.

Another approach is to follow a javadoc model. Put it in an #IF .F., bracking a TEXT ENDTEXT, directly in the method and parse it out with a doc tool (it's easy to write one to your own requirements). This is less convenient but more flexible.

However, in 9, you may want to try adding custom attributes into Memberdata for this purpose. A lot easier to parse and doc-centric Memberdata attributes can be standardized in the Fox community more easily as well. Plus you can share this type of approach between reports and classes, since they use the same Memberdata XSD.

>L<