|Jul 27, 2007, 05:52 PM||#1|
I have realised that the source code for my application is well, very poor, so I've been trying to get my documentation up to scratch, I tried using HeaderDoc, but Apple seem to have abandoned it and it is very buggy (it adds a month to dates, so thinks today is the 27th August) and it is difficult to get to parse the code.
Anyhow what can I use? I am programming in Objective C so sadly (I guess) can't use Javadoc, which is excellent.
EDIT: Attached is the relevent header file, and the documentation folder in a zip, apart from the dates I may be being a little unfair about HeaderDoc so I'll take another look tomorrow, but good documentation comments are still welcome.
Last edited by Eraserhead; Jul 27, 2007 at 06:09 PM. Reason: Adding attachment/edit
|Jul 27, 2007, 06:24 PM||#2|
Beyond that, it is useful to have documentation that explains how a class is used. Automatic tools usually don't do that, because they just document individual functions. And as I said, with well-written code that kind of documentation doesn't add very much.
|Thread Tools||Search this Thread|
|thread||Thread Starter||Forum||Replies||Last Post|
|Write documents in two languages?||amiralberthanna||Mac Basics and Help||1||Nov 27, 2010 02:06 AM|
|Another write privileges problem w/ iTunes||poodlefan311||Mac Applications and Mac App Store||2||Nov 4, 2010 12:12 AM|
|Software for writing documents||moofasa||Mac Basics and Help||3||Apr 27, 2009 08:41 PM|
All times are GMT -5. The time now is 02:47 PM.