Logged two new issues:

• Issue 0174 - Bug#195282: ccdoc: FTBFS with g++-3.
• Issue 0175 - Generate an index in HTML and XML.

Released a new version of ccdoc (r40) that fixes issues 0172 and 0173.

I will be on vacation until mid-June so no work will be done on ccdoc during that time.

Logged a new issue:

• Issue 0173 - The md5hash macro is being improperly ignored by the rptmac1 heuristic.

This issue has been fixed in r40 (not yet released).

I will release r40 in the next couple of days.

Logged a new issue:

• Issue 0172 - Template friend declarations are not resolved properly when packages are used.

This issue has been fixed in r40 (not yet released). If this is a critical problem for you, please let me know and I will spin a release.

Mar 03, 2003
Monday

A new version of ccdoc: v08r39, is available with the following changes:

• Converted all of the source files to unix format for the upcoming release to cygwin (ccdoc-0.8.39-1).
• Converted all of the source files to unix format for the upcoming release to cygwin (ccdoc-0.8.39-1).
• Created a cygwin compatible release package (with lots of help from the cygwin folks). The package provides a man page, a configure script, patches, etc. This might be useful for folks that want to support ccdoc on linux platforms. I will add a link to the cygwin package when it is officially accepted.
• Improved the man page generation (also for cygwin). There were still a number of problems in r38. The r39 man page is now readable.
• Removed dead code found by Christian Ehrlicher during his port to the Borland compiler.
• Issue 0152 - Ignore duplicate macros names. This surfaced during r39 testing. I found a case where duplicate macros were reported when they were defined in different packages.
• Issue 0167 - In German we want to use embedded dots in the short description.
• Issue 0168 - Slow g++ 3.2 compile of help.cc because of the large help string.
• Issue 0169 - Man page has formatting problems.
• Issue 0170 - Bug on NT platforms parsing command line with spaces and wildcards.
• Issue 0171 - Constructors with constructed default arguments are reported with the wrong method name.
• Added _INCLUDED and _included suffixes to the -rtpmac1 heuristics.

The following issues have been reported and will be fixed in the upcoming v08r39 release. Please contact me if you need any of these fixes now.

• Converted all of the source files to unix format for the upcoming release to cygwin.
• Removed dead code found by Christian Ehrlicher during his port to the Borland compiler

The following issues have been reported and will be fixed in the upcoming v08r39 release. Please contact me if you need any of these fixes now.

• Issue 0152 - Ignore duplicate macros names. This resurfaced during r39 testing. I found a case where duplicate macros were reported when they were defined in different packages.
• Issue 0170 - Bug on NT platforms parsing command line with spaces and wildcards.
• Issue 0171 - Constructors with constructed default arguments are reported with the wrong method name.
• Improved the man page generation. There were still a number of problems. The r39 man page is now readable.
• Added _INCLUDED and _included suffixes to the -rtpmac1 heuristics.

The following issues have been reported and will be fixed in the upcoming v08r39 release. Please contact me if you need any of these fixes now.

• Issue 0167 - In German we want to use embedded dots in the short description.
• Issue 0168 - Slow g++ 3.2 compile of help.cc because of the large help string.
• Issue 0169 - Man page has formatting problems.

A new version of ccdoc: v08r38, is available that has extensive updates to the on-line help.

It is very similar in function to v08r37. The only differences are:

• It officially supports the @endlink directive.
• It ignores macros with the _INCLUDED_ suffix in -rptmac1 mode.
• Issue 0166 was fixed.

There are a number of infra-structure changes. I added a script to automatically update the downloads page and removed the Makefile dependency on the set_release_info script. None of the infra-structure changes affect the program.

I also added the FAQ.

A new version of ccdoc v08r37 is available that fixes the bugs described by the following issues:

• 0157 - In some cases operator code is being processed incorrectly.
• 0158 - Class method implementations are reported as global functions.
• 0159 - Very long names make the contents table very hard to read.
• 0160 - Empty function names appear under certain conditions.
• 0161 - Strange function names like "max)" appear sometimes.
• 0162 - Doxygen compatibility - support single line comments using doxygen syntax.
• 0163 - Doxygen compatibility - ignore the @endlink directive.
• 0164 - Doxygen compatibility - ignore @file comment blocks.

This release was made because this version actually successfully parsed an STL release!

The best practices document was also updated to include namespace and template sections.

Be careful, there was an intermediate version of r37 that was available for a couple of days because of source forge compile farm problems. To make sure that you have the correct version of r37 look for the -doxygen switch in the help.

A new version of ccdoc v08r36 is available that fixes the bugs described by the following issues:

• 0156 - More namespace problems in r35.

This release was made because this was a critical bug.

Two new bugs were reported.

These have already been fixed in the working version of r37 and will be released later this week.

• 0157 - In some cases operator code is being processed incorrectly.
• 0158 - Class method implementations are reported as global functions.

A new version of ccdoc v08r35 is available that fixes the bugs described by the following issues:

• 0154 - Eliminate the requirement that the -rptmac and -rptmac1 switches appear in phase 1.
• 0155 - Incorrect documentation when there is only one ccdoc namespace comment for namespace declarations in multiple files.

This release was made because the r34 requirement that -rptmac and -rptmac1 switches appear in phase 1 was inconsistent with the interface paradigm.

A new version of ccdoc v08r34 is available that fixes the bugs described by the following issues:

0056 - Incorrect line numbers reported in warning messages.
• 0098 - It would be a help if you made the reference red if the class cannot be found for @link.
• 0107 - javadoc # syntax is not supported in the {@link...} directive.
• 0109 - Print warnings to stderr.
• 0122 - Enhance template reporting.
• 0149- Template method implementations confuse ccdoc. There was a corner case that was not handled properly.
• 0150 - Make it easier to update the revision number in the source files.
• 0152 - Ignore duplicate macros names.
• 0153 - Add a heuristic to ignore include guards and DLLIMPORT macros.

This release was made because a user had a critical need for the 0149 fix and because I had some time.

A new version of ccdoc v08r33 is available that fixes the bugs described by issues

• 0144 - Mark static members and methods in the class overview.
• 0149- Template method implementations confuse ccdoc.

This release was made because a user had a critical need for the 0149 fix.

A new version of ccdoc v08r32 is available that fixes the bugs described by issues

• 0146 - Namespace processing doesn't work properly in certain cases.
• 0147- Lots of compiler warnings when building ccdoc using the Borland C++ compiler.

This release was made because a user had a critical need for the 0146 fix.

Two new ports are available:

1. CerfCube SA1110 - Debian 3.0
2. x86 - Freebsd 4.7
   

Added four new issues:

• 0141 - Architecture is not reflected in the bin directory name.
• 0142 - No man page for linux ports.
• 0143 - Support javadocs frames format.
• 0144 - Mark static members and methods in the class overview.

Couldn't do the CerfCube port because there was a problem at the source forge compile farm. I will release it when that platform becomes available.

Added the MacOS X 10.1 port.

A new version of ccdoc v08r29 has been released that fixes issues 0138 and 0139. These bug fixes were considered serious enough to warrant a new release. In addition the copyright notice was updated and the issues list was added to the project page.

I figured out how to use the compile farm and was able to successfully port to a number of new platforms.

Updated the counter script to allow users to add keys by id. This allows multiple users to share the same counter file. I also added a bunch of examples that show how to use the script in the help.

Uploaded all of the ccdoc source to the sourceforge.net CVS repository and added the sourceforge log to this page per their request.

I still need to figure out how to organize the release to make it source forge like but for now you should be able to get everything that you need.

Finally completed the counter perl script (see the downloads page) and all of the executables. The project release has been officially moved to ccdoc.sourceforge.net!

I still need to update the CVS repository.

Changed the look and feel of the main page to make it much simpler (ala google - no frames, no fancy stuff). Also updated almost all of the documents in the system to bring them up to date and to check for consistency. Beefed up the introduction to show how to use the tool (simplistically).

Many thanks to Ragav Satish for suggestions on simplifying the interface.

Moved the project documentation to sourceforge.net (http://ccdoc.sourceforge.net). I still need to move the source into the sourceforge CVS repository and update www.joelinoff.com/ccdoc. That should happen tomorrow.

Found a bug and logged it as issue 0137. There is a workaround (that is described in the issue entry) so the fix is not urgent.

• 0137 - The {@link} directive does not work @param clauses.

In other news, I have moved my development environment to version 3.2.3 of the gcc compiler (from cygwin).

Nov 18, 2002
Tuesday

Added a link on the downloads page to the ccdoc port that Dieter Habelitz did to RISC OS. Details can be found here.

Nov 14, 2002
Thursday

A new version of ccdoc r28 has been released one day after r27! This was done because a critical bug was found for nested structures/classes (issue 0136). The following issues have been fixed in r28:

• 0135 - Fix the copyright notice in the code.
• 0136 - Ccdoc gets confused by a nested struct.

Updated the users guide for r27 and added a new best practices document. The porting is complete and I am now running system tests. When these have been verified, ccdoc v08r27 will be released.

The systems tests have completed successfully which means that r27 will be released today with the following fixes:

• 0120 - Add support for the proposed todo tag in javadoc.
• 0123 - {@link ...} not reported correctly in the @deprecated directive.
• 0124 - Scanner condition evaluates to a constant value.
• 0125 - Hash mark displayed for default {@link...} reference.
• 0127 - CcDoc does not recognize recognize template derivations.
• 0129 - All subdirectories are picked up on NT when the * wildcard is specified.
• 0130 - Code section wraps in a strange way for small browser windows.
• 0133 - Anonymous namespaces are not handled correctly.
• 0134 - Need a forward link to the contents section for classes and packages

In addition the users guide has been updated to reflect the introduction of the @todo directive and the new switches -[no]rptcfuns.

After the release was finished I came across an interesting discussion about the ccdoc license in the linux.debian.legal newsgroup. I have added it as issue 0135 and have updated the source code for r28. For those of you that are interested in all things legal, the new copyright notice supercedes the previous copyright notice for all prior releases.

All bug fixes and enhancements are complete for r27. I am currently porting and expect to be finished by the end of the week.

Nov 11, 2002
Monday

The results of the survey are in. I will continue to fully support ccdoc. 100% of the respondents, about 25, voted to NOT merge with Doxygen. Many of them (>75%) use both doxygen and ccdoc (I also use both) but they liked using ccdoc as the interface documentation.

As far as supporting ccdoc goes, r27 is almost ready for release. The following bugs have been fixed.

• 0120 - Add support for the proposed todo tag in javadoc.
• 0123 - {@link ...} not reported correctly in the @deprecated directive.
• 0124 - Scanner condition evaluates to a constant value.
• 0125 - Hash mark displayed for default {@link...} reference.
• 0127 - CcDoc does not recognize recognize template derivations.
• 0129 - All subdirectories are picked up on NT when the * wildcard is specified.
• 0130 - Code section wraps in a strange way for small browser windows.
• 0134 - Need a forward link to the contents section for classes and packages.

The following bug is scheduled to be fixed before r27 is released.

• 0133 - Anonymous namespaces are not handled correctly.

I am actively working on it and hope to finish by the end of the week.

I am back and am actively working on r27. There are a few critical bugs that must be fixed for this release. They are:

• 0127: CcDoc does not recognize recognize template derivations.
• 0133: anonymous namespaces are not handled correctly

The following bugs/issues have been reported since March 15th:

• 0131: Support comma separated declarations.
• 0132: support single-line prefix comments via //@+
• 0133: Anonymous namespaces are not handled correctly.

I have been looking at using XML (schema) as the optional output for the backend in r28. Please feel free to let me know what you think of this approach.

I have been completely lame about updating my web pages and have received a lot of mail from folks asking whether ccdoc is still being supported. The answer yes, here is what I have been doing.

• Planning for the next release (r27).
• Fixing some bugs.
• Working on XML output.
• Looking at whether doxygen can replace ccdoc.

The last bullet probably requires some explanation.

A number of folks have suggested that ccdoc be combined with doxygen (a very good source code documentation and browsing system). Since I really didn't know much about doxygen I looked into it. My conclusion is that doxygen is much more that ccdoc will ever be.

The development team has done a great job of developing a tool that documents and provides source code browsing for C++ projects and I strongly recommend it.

Ccdoc is only meant to document interfaces so there is no question that doxygen is a superset of ccdoc from a functional perspective.

From a project standpoint, I am still trying to understand what ccdoc users want. A few of them have reported that they really like the interface only approach and some users even use both tools. I am still polling and have currently decided to continue to support ccdoc to the best of my ability.

Please let me know what you think. Here are the choices:

1. Continue to support ccdoc as an interface documentation tool.
2. Cease work on ccdoc and work with the doxygen team to get ccdoc like output.

Two new bugs were reported:

• 0129 - All subdirectories are picked up on NT when the * wildcard is specified.
• 0130 - Code section wraps in a strange way for small browser windows.

Found another bug (and work around):

• 0127 - CcDoc does not recognize recognize template derivations.
• 0128 - Order class entities the same way that were ordered in v07.

I actually took a bit more than a month off but now I am back. Here is the summary of the latest bugs:

• 0123 - {@link ...} not reported correctly in the @deprecated directive.
• 0124 - Scanner condition evaluates to a constant value.
• 0125 - Hash mark displayed for default {@link...} reference.
• 0126 - CcDoc does not recognize ccdoc c++ short comment in a "typedef struct" definition.

Here are some of the things that I am looking at in the near future for ccdoc:

• XML output (on the perennial list)
• User defined directives. The idea here is that users could define their own custom directives to extend ccdoc for their environment.

I am taking a month off from ccdoc to get some rest. I will get back to it in January 2002.

Please keep sending suggestions and bug reports, I will archive them and when I get back, catalogue them as issues.

Happy Holidays.

A new release of ccdoc is available: "ccdoc v0.8 r26 2001/11/28".

This release fixes the following issues:

• 0086 - Comment form to handle single line suffix comments.
• 0099 - Ccdoc does not correctly follow the standard for default constructors.
• 0101 - Template problem.
• 0102 - Returned nested classes and types in namespaces are not recognized correctly.
• 0114 - Error processing of a operator unsigned long().
• 0115 - Mangled links for .\doc\ references on the command line.
• 0116 - The string constant "\\" isn't parsed correctly.
• 0117 - Class method reported as global function.
• 0118 - Resolve partially scoped references

Two new issues added against r25

• 0121 - Reuse namespace comments between packages.
• 0122 - Enhance template reporting

Fixed the following issues in r26:

• 0099 - Ccdoc does not correctly follow the standard for default constructors.

Added another new issue against r25:

• 0120 - Add support for the proposed todo tag in javadoc

Fixed the following issues in r26:

• 0101 - Template problem.

Added another new issue against r25:

• 0119 - Inconsistent command line syntax for -html paths under DOS

Six new issues have been reported since the r25 release.

• 0113 - Merge separate ccdoc databases.
• 0114 - Error processing of a operator unsigned long().
• 0115 - Mangled links for .\doc\ references on the command line.
• 0116 - The string constant "\\" isn't parsed correctly.
• 0117 - Class method reported as global function.
• 0118 - Resolve partially scoped references.

I have already fixed 0114, 0116, 0117 and 0118. I will release r26 with these fixes by next Monday. If you are having serious problems with any of the above issues, please send me e-mail and I will release r26 sooner.

In addition, a new feature has been added (as described by 0086). This feature was requested and implemented by Ben Zoe. It allows you to specify a C++ style, single line, suffix comments as shown in the example below:

class Point3D {
public:
  int p1; //@- The x coordinate.
  int p2; //@- The y coordinate.
  int p3; //@- The z coordinate.
};

Important! I released ccdoc v0.8 r25 twice today. The first had a date of 2001/11/17 which was incorrect. The correct version has a date of 2001/11/19. Please re-download when you get the chance.

A new release of ccdoc is available: "ccdoc v0.8 r25 2001/11/19". The following issues were fixed.

• 0095 - Comma's inserted for each line in @returns and @deprecated comments.
• 0097 - Private method is reported incorrectly for overloaded methods with different scopes.
• 0100 - If using switch -files with a wildcard expression the first file is not processed.
• 0103 - Invalid processing of operator~().
• 0104 - Invalid processing of operator&().
• 0110 - Invalid processing of operator[]().
• 0111 - Multiple link file overflow problem.
• 0112 - Phase 3 exception for operator |.

I was not able to do as much in this release as I had hoped because of other commitments but these fixes (especially 0095) generated a lot of bug reports so I wanted to get them out as soon as possible.

Twelve new issues were added today.

• 0098 - It would be a help if you made the reference red if the class cannot be found for @link.
• 0099 - Ccdoc does not correctly follow the standard for default constructors.
• 0100 - If using switch -files with a wildcard expression the first file is not processed.
• 0101 - Template problem.
• 0102 - Returned nested classes and types in namespaces are not recognized correctly.
• 0103 - Invalid processing of operator~().
• 0104 - Invalid processing of operator&().
• 0105 - The javadoc @see tag defines the label part as optional.
• 0106 - The javadoc spec for @see allows unqualified names as well as qualified names.
• 0107 - javadoc # syntax is not supported int the {@link...} directive.
• 0108 - -rptdefasd, -rptdefsd and -rptdefv problems and suggestions
• 0109 - Print warnings to stderr.
• 0110 - Invalid processing of operator[]().

I have already fixed or closed issues 0095, 0097, 0100, 0103, 0104 and 0110 for r25. I will do as much as I can to get more bug fixes in before next Monday's release of r25 but I am very busy with other stuff right now so don't expect too much.

Another new issue has been added:

• 0097 - Private method is reported incorrectly for overloaded methods with different scopes.

Two new issues have been added:

• 0095 - Comma's inserted for each line in @returns and @deprecated comments.
• 0096 - Provide an @repeat operator to avoid having to re-type comments.

Issues 0093, 0094 and 0096 seem to address the common theme of reducing the need to type redundant comments. I am actively looking into this.

Two interesting issues have been added:

• 0093 - Add javadoc style doc comment inheritance.
• 0094 - Comment reuse for overloaded functions.

I really like the notion of comment inheritance and will see whether it can be added in the near future.

In addition, one user reported problems with ccdocv08r24 under cygwin on windows. I have not been able to duplicate the problem and I have heard from other cygwin users that it works for them so it hasn't been entered as an issue -- yet. Please let me know if you have similar problems.

A new release of ccdoc is available: "ccdoc v0.8 r24 2001/10/26".

This release fixes the following issues:

• 0079 - platform.pl cannot handle embedded parentheses.
• 0080 - Trim trailing spaces in path name for get_stmt_no_pkgs().
• 0081 - Multi-space blank lines between SHORT and LONG descriptions cause them to merge.
• 0082 - Add the @since directive per the javadoc 1.2 specification.
• 0083 - Modify ccdoc to create a separate links page (as was done in v0.7a).
• 0084 - Alias @exception to @throws per javadoc 1.2.
• 0085 - Ccdoc not recognize default constructors with member initialization.
• 0087 - Exceptions were not reported as links.
• 0088 - An extra invalid link reported for @link references to classes.
• 0089 - Ccdoc short description syntax is not compliant with javadoc.
• 0090 - Support the {@link ...} javadoc syntax.
• 0091 - Constant values are not hyperlinked in the documentation for function arguments.
• 0092 - The @link syntax does not support the # scoping operator.

Note that the fix for issue 0082 will change the database contents so you will have to re-generate your databases. This is because the comment schema was modified to accomodate the new @since directive. I consider this intrusion acceptable because all clients that I know of re-generate the databases each time they run.

Note that the fix for issue 0089 will change your HTML output because the javadoc syntax for short descriptions is different than the old ccdoc syntax. You can use the old ccdoc style syntax by specifying the -nojdsd switch. I decided to make the javadoc syntax the default because the behavior ccdoc input syntax is supposed to conform as closely as possible to javadoc semantics. The users guide has been updated to reflect this behavior.

Note that the users guide has been updated to reflect the new @since, @throws and {@link...} support.

A number of new issues have been reported. The bold issues have already been fixed in r24.

• 0079 - platform.pl cannot handle embedded parentheses.
• 0080 - Trim trailing spaces in path name for get_stmt_no_pkgs().
• 0081 - Multi-space blank lines between SHORT and LONG descriptions cause them to merge.
• 0082 - Add the @since directive per the javadoc 1.2 specification.
• 0083 - Modify ccdoc to create a separate links page (as was done in v0.7a).
• 0084 - Alias @exception to @throws per javadoc 1.2.
• 0085 - Ccdoc not recognize default constructors with member initialization.
• 0086 - Comment form to handle single line suffix comments.
• 0087 - Exceptions were not reported as links.
• 0088 - An extra invalid link reported for @link references to classes.
• 0089 - Ccdoc short description syntax is not compliant with javadoc.
• 0090 - Support the {@link ...} javadoc syntax.
• 0091 - Constant values are not hyperlinked in the documentation for function arguments.

A new release of ccdoc is available: "ccdoc v0.8 r23 2001/10/19".

This release fixes the following issues:

• 0075 - Ccdoc cannot handle function typedef of the form: typedef void fct(int arg1);
• 0076 - Conflict between -meta switch and ccdoc defined meta variables.
• 0077 - Ccdoc incorrectly identifies a class attribute name.
• 0078 - Ccdoc incorrectly identifies a variable as a function.

Two issues have reported against r22. These are already fixed in r23 and will be released at the end of this week or early next week. Here are the details:

• 0075 - Ccdoc cannot handle function typedef of the form: typedef void fct(int arg1);
• 0076 - Conflict between -meta switch and ccdoc defined meta variables.

The new release of ccdoc is available: "ccdoc v0.8 r22 2001/10/12".

This release fixes the following issues:

• 0069 - Cannot handle construct: "Float operator/(const Float & rval)"
• 0070 - Users guide documentation error.
• 0071 - Operator keyword duplicated for method operators.
• 0072 - New switch to turn off sorting of class entities.
• 0073 - Can't tell ccdoc to ignore a privately declared default constructor.
• 0074 - Ccdoc cannot handle international character sets.

The new release of ccdoc is available: "ccdoc v0.8 r21 2001/10/01".

This release fixes issues 0064, 0066 and 0068. It was triggered by 0068 which was a critical bug fix.

No one responded to my request to keep the solaris 2.4 port so it has been dropped from this release.

The new release of ccdoc is available: "ccdoc v0.8 r20 2001/09/24".

This release fixes issues 0063.

The new release of ccdoc is available: "ccdoc v0.8 r19 2001/09/21".

This release fixes issues 0053, 0054 and 0059.

Issues 0055, 0057 and 0058 have been closed.

The ccdoc generated web pages are now compliant with the HTML 4.01 Transitional specification.

The Solaris 2.4 port will be dropped in the next release because no-one seems to be using it. If you want me to continue to support this version, please send me e-mail as soon as possible.

Added issues 0054, 0055, 0056, 0057, 0058, 0059 and 0060.

Also validated the issues pages to make sure that they are HTML 3.2 compliant using the verifier described in issue 0059.

The new release of ccdoc is available: "ccdoc v0.8 r18 2001/09/18".

This release fixes issues 0052 and is the first release that contains the linux port.

The new release of ccdoc is available: "ccdoc v0.8 r17 2001/09/11".

This release fixes issues 0047, 0048, 0050 and re-fixes issue 0045.

There were two new releases of ccdoc today: "ccdoc v0.8 r16 2001/09/10" and "ccdoc v0.8 r15 2001/09/10".

The reason for r16 is that a bug (0046) that was easy to fix was reported about half an hour after r15 was published. This bug fix was important for the user so I decided to re-release quickly.

The r15 release fixes issues 0041, 0042, 0043, 0044, and 0045. Updated the users guide to reflect changes that occurred as the result of these fixes.

The new release of ccdoc is available: "ccdoc v0.8 r14 2001/09/07".

This release fixes issue 0039. This fix significantly improves ccdoc run time in phases 2 and 3. It has no other affect.

The new release of ccdoc is available: "ccdoc v0.8 r13 2001/09/06".

This release fixes the following issues: 0037, 0038 and 0040.

Issue 0039 is still being worked on.

The new release of ccdoc is available: "ccdoc v0.8 r12 2001/09/04".

This version adds a quick reference guide was added (issue 0035) to provide highlights of new features in v0.8 that will be of interest to users of 0.7a and it fixes issue 0036.

A new release of ccdoc is available: "ccdoc v0.8 r11 2001/09/02".

It provides a fix for issue 0034 (the -rpthpc switch was too verbose). This fix won't be available for Solaris until next Tuesday.

A new release of ccdoc is available: "ccdoc v0.8 r10 2001/08/30".

It supports the resolution of issue 0007, support for wildcards under MS windows in the MS-DOS command interpreter.

It also provides fixes for the following issues: 0026, 0027, 0028, 0029, 0030, 0031, 0032 and 0033.

A new release of ccdoc is available: "ccdoc v0.8 r9 2001/08/29".

Issues 0024 and 0025 were fixed in r9.

A new release of ccdoc is available: "ccdoc v0.8 r8 2001/08/28".

Issues 0020, 0021 and 0022 were fixed in r8.

Added issues 0015, 0016, 0017, 0018, 0019, 0020, 0021 and 0022.

A -version switch was added to make it easier to determine which release of v0.8 you have (issue 0017).

Added issues 0011, 0012, 0013 and 0014.

Issue 0013: I am in the processing of adding ccdoc to source forge (http://sourceforge.net). Today they approved the project!

Fixed issue 0014 and re-released 0.8.

Added some new issues.

Updated the users guide to document the new -meta switch and the -[no]cdsm switches.

Fixed issue 0004 by renaming the download files.

Closed issue 0007. This is a known problem with a workaround.

Fixed issue 0008. Added a new switch to phase 1 called -[no]cdsm to turn on or off the default creation of special members that are not explicitly defined by the class.

Fixed issue 0009.

Fixed issue 0010.

Created the issues section for the newly reported bugs and enhancement requests.

Fixed issues 0001, 0002, 0003, 0005 and 0006.

Released new versions of the executables with these fixes.

The following switches were not implemented due to an oversight:

• -[no]rptmac
• -[no]rpttype
• -[no]rptun

Many thanks to Dániel Dékány for promptly pointing out the problem.

I have fixed the problem and have released the updated version of ccdoc.

To determine whether you have a broken version specify -rptmac on the command line. If you get an error about a missing file, you have the old version. You can workaround this problem by specifying -macros or -no macros or you can fix the problem by downloading the most recent version of the release.

CcDoc version 0.8 has been released on the following platforms:

• Windows
• SunOs 5.6
• SunOs 5.8
• HP UX
• Linux

Here is a brief overview of some of the new features:

• The HTML files names do not change between runs so you can now link to them safely.
• Namespaces are supported.
• Inherited methods are reported.
• Pre-processing expressions are now fully supported.
• A hierarchical class summary is generated.
• The output format has changed. It is much simpler.
• The program has been completely rewritten to take advantage of STL.