…rser and new clang pedantry.
Added cross referencing for top-level defined blocks Implement simple cross referencing within method outputs Fixed compiler warnings about missing [super dealloc]s Fixed possible bug for constants in stringByConvertingSimpleCrossReferencesInString: cross reference prevention Fixed compiling with latest xcode
…rather then unknown warning.
This provides much simpler handling of the change in 3485e41
This is with an eye toward converting to ARC, which does not like having NSObjects in structs, and also makes the code more readable.
Fixes #349 and failing test case: ``` GBCommentsProcessorRegistrationsTesting testProcessCommentWithContextStore_combinations_shouldRegisterMethodDescriptionBlock ```
When a link falls within another link, such as a URL string within a method call, processing both would result in the processed URL being appended to the processed method call, duplicating the text from the URL. Instead, keep track of the links processed, and ignore a link if it's inside of a previously processed link. Here's a test case which illustrates the problem: ```objc /** `NSURL *baseURL = [NSURL URLWithString:@"http://example.com/v1/"]` */ @interface Fooclass : NSObject @end ``` Result: ```html <p><code>NSURL *baseURL = [NSURL URLWithString:@"http://example.com/v1/"]</code>http://example.com/v1/<code>"]</code></p> ``` With patch: ```html <p><code>NSURL *baseURL = [NSURL URLWithString:@"http://example.com/v1/"]</code></p> ``` The test case does indeed cover this problem but certainly could be improved.
…ce methods to the code order.
The regression was introduced with one of recent contributions. My guess is the contributor was using older code base and didn't update before issuing pull request. The same issue repeated second time, to prevent further regressions, I added a comment to source code specifically guarding against changing affected lines. Not the best approach, but at least something until 3.0 is out...
…thod] now works) and markdown generation. Refs #237
…with custom title. Refs #237
…ginal name is nil. Closes #199.
Add support for printing titles of information blocks. Apple displays "Note:" in bold at the start of their note documentation. We'd like to do the same for warnings and bugs. This is now the default, and can be turned turned on/off with the 'print-information-block-titles' setting.
…resses #117. This is on by default, but can be controlled through `--merge-category-comment` cmd line switch.
The problem with star delimited unordered lists was in appledoc comment preprocessor which consumed single star and replaced them with double star markers so that text would be emitted in bold. That's actually a feature of appledoc which allows single stars be used for bold markers, but may break compatibility with Markdown as the result. As there's no reliable way of determining whether the user wants to have star delimited, I decided to go the route I had in my mind for some time now: introduce another command line switch that would prevent handling single stars. It's on/off solution, so not the best one, but everyone can choose at least... Also updated [online documentation](http://gentlebytes.com/appledoc-docs-examples-basic/index.html#compatibility) with example of using the new switch. **Important:** As of this version on, single star handling is **off** by default! This may break backwards compatibility with some folks, but I feel it's better to keep as Markdown compatible for new people as possible...
This is useful if you only want to generate documentation for certain sources but those sources depend on other sources that should not have documentation generated for them. With this feature, you add all sources as input and exclude certain sources from output generation. It will hide warnings on excluded sources, not generate output for them, but they will be used for merging with your included sources (eg. inheritance etc.)