Thomas Thomassen

@lsegal - any chance you are able to shed some light on the differences between the Ruby and the C parser? Something that let me avoid the kludge I currently...

I had another look at this again. Reverted my hacks, kept the spec. What I'm seeing is that the `DirectiveParserHandler` is executed after `YARD::Handlers::C::ConstantHandler` so that the group directive have...

Can this relate to differences in how Ruby and C is parsed? Ruby appear to traverse via the AST tree, where as C appear to be parsed by regex extraction,...

Here are my observations: ``` SourceParser#parse ... @parser.parse post_process ``` After `@parser.parse` is done `@parser.enumerator` (`@statements`) contains six items; one `TopLevelStatement` and five `Comment`s. The `TopLevelStatement` contains four `BodyStatement`. ```...

I haven't been able to figure out a solution that avoids copying the `@!group` back into the ` ToplevelStatement` node. To avoid that the C parser might have to change...

@lsegal - any chance you have time to consider questions in earlier comment? https://github.com/lsegal/yard/pull/1238#issuecomment-530010441 The current way C source is parsed and information stores doesn't seem to fit with the...

I'm having another look at this. @lsegal do you have a spare moment to look at my earlier question in this comment: https://github.com/lsegal/yard/pull/1238#issuecomment-530010441 ? I'd help me in what direction...

Didn't know the Ruby headers had a macro for that. We have been using our own macro for our C++ application: https://github.com/SketchUp/ruby-c-extension-examples/blob/master/Hello%20World/src/RubyUtils/RubyUtils.h#L21 That's been working for us, along with YARD...

I checked again. and I think my original description wasn't entirely accurate. With a clean project, `yard stats --list-undoc` only generate `.yardoc`. However, this Rake task will generate docs: ```rb...

We've run into the same issue, were we used YARD to reformat the doc-comments. However, it appear to sort tags alphabetically. Where our original source code have had them organized...