はてなブックマーク

A while back I posted instructions for how to document Objective-C with Doxygen. In part 2 I published a very basic helper script to make it less onerous to document code in Xcode 3. While the script wasn’t perfect, I think it using it was definitely more convenient than writing every documentation comment entirely by hand. One of the changes in Xcode 4 is that there is no support for user defined

You are seeing this because the administrator of this website has set up Anubis to protect the server against the scourge of AI companies aggressively scraping websites. This can and does cause downtime for the websites, which makes their resources inaccessible for everyone. Anubis is a compromise. Anubis uses a Proof-of-Work scheme in the vein of Hashcash, a proposed proof-of-work scheme for redu

This approach no longer works with Xcode 4. Read Using the Doxygen Helper in Xcode 4 for a work around. In part I I covered how to comment your code with javdoc style comments that can be extracted into html documents or other types of output. What I want to cover in this post is how to incorporate documenting your code into your workflow. The first problem to tackle is the additional overhead inc

You are seeing this because the administrator of this website has set up Anubis to protect the server against the scourge of AI companies aggressively scraping websites. This can and does cause downtime for the websites, which makes their resources inaccessible for everyone. Anubis is a compromise. Anubis uses a Proof-of-Work scheme in the vein of Hashcash, a proposed proof-of-work scheme for redu