objective c - What Doxygen alternative would Dave DeLong use? -

-

here's sure way downvoted, kickbanned , laughed at, i'm gonna try anyway.

yesterday dave delong answered a question of mine. wasn't answer looking for, in question mentioned alternative way of generating doxygen-style documentation objective-c.

before it, (maybe dave himself) noticed answer didn't match question , removed it. *poof* gone link documentation tool.

i can't remember name, i'm it's neither headerdoc nor doxygen itself.

dave, out there? link again?

may gods of downvoting gentle me. cheers y'all,
ep

p.s. where's "send message user" button on stackoverflow again? :s

i'm not dave delong, i'd use appledoc, it's pretty darn awesome!

developer page quote:

appledoc command line tool helps objective-c developers generate apple-like source code documentation specially formatted source code comments. it's designed take readable source code comments possible input , use comments surrounding source code generate visually appealing documentation in form of html indexed , browsable xcode documentation set. although there several tools can create html documentation objective-c, of know me fall short in meeting minimum of goals described below.

human readable source code appledoc designed keep source code comments readable possible within source code editor.

cross references objects , members creating cross references classes, categories or protocols straightforward , automated possible.

apple-like source code html documentation generate appealing html documentation same style apple's.

xcode documentation set creation generate , install indexed , browsable xcode documentation sets. documentation set can automatically installed xcode.

single tool sorce code doc set single tool drive generation source code parsing documentation set installation

easily customizable output appledoc gives lot of command line switches can parameterize output. if not enough, can change or of template files suit needs.

100% objective-c implementation whole appledoc written in objective-c, can change using familiar language , tools. make debugging simpler , effective.


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more