<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>keith wrote:<br><blockquote type="cite">Not forgetting of course that you can mark documentation methods with a pragma.<br></blockquote><blockquote type="cite">I could be wrong but I think that the the #compilerClass call only works for overriding instance side method behaviour,<br></blockquote><blockquote type="cite">the hack would have to be more universal (or attached to MetaClass >> compilerClass ) for other methods.<br></blockquote><blockquote type="cite">Ok it is hacky, but it is "very" useful. If you have a better idea, which I am sure you do I am all ears. <br></blockquote><br>This is definitely useful although I'd like to think a little bit harder about the syntax to choose. However, for the purpose of writing documentation for a class or subsystem I'd still say that a class comment is a great place to put it :-)<br><br>Cheers,<br> - Andreas<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>We had/have the text of the whole of Mantis exported into Methods, for reading/searching in the image.</div><div><br></div><div>Keith</div></body></html>