Commit graph

10 commits

Author SHA1 Message Date
Tilman Keskinoz
2053078b32 Fix build with gcc34 2004-06-12 20:03:07 +00:00
Greg Lewis
4f1a10ad44 . Update to 0.8r40 (which will hopefully unbreak 5.x). 2004-02-17 18:30:00 +00:00
Trevor Johnson
0c881ba59c SIZEify. 2004-01-29 07:24:56 +00:00
Mark Linimon
cb16459fae Mark as broken on 5.x (stricter gcc3.3 string continuation handling). 2003-12-08 06:40:45 +00:00
Trevor Johnson
e99ceadaf6 Use the FIND and XARGS macros introduced in bsd.port.mk 1.391. 2003-11-13 14:45:08 +00:00
Kris Kennaway
f129356ddc Reset bouncing maintainer address 2003-10-13 10:33:55 +00:00
Sergey A. Osokin
f37f7775e3 Make portlint(1) happy by changing strip to ${STRIP_CMD}
Submitted by:	Oleg Karachevtsev <ok@etrust.ru>
PR:		56998
2003-09-24 09:37:11 +00:00
Akinori MUSHA
65dac0040a De-pkg-comment. 2003-02-21 11:23:04 +00:00
Pete Fritchman
0c49864419 Fix typo: USE_PERL -> USE_PERL5 2002-06-02 19:22:16 +00:00
Dirk Meyer
85b7674614 - port converted in new layout
- textproc added in category (like astyle)

Ccdoc is a tool for extracting comments from C++ source code and presenting it
in HTML format, very similar to Java's JavaDoc tool. The tagging used in ccdoc
is very similar to that of Javadoc, with adaptations for the C++ specifics, of
course. Ccdoc supports extracting comments from both header and implementation
files.

In contrast to most other C++ doc'ing applications, ccdoc analyses the code
before it has been run through the pre-processor, so things such as macros can
actually be included in the documentation.

It's usage is not quite as straight forward as JavaDoc's, but considering the
quality of the output, it is well worth the effort.

WWW: http://www.joelinoff.com/ccdoc/

PR:		22794
Submitted by:	lonewolf@flame.org
2001-03-14 16:24:40 +00:00