[nesting] path construction in comment parser

[secretrobotron]

1. Implemented simple path construction (adjustPath) in parseComments.
2. Added test.
3. Added a fixture for said test.

Without disrupting the way dox already constructs its output, this patch offers a way for people to use the output to build nested structure. For example, having a class with members: paths offer some insight into how your documentation can be structured.

[tj]

hmm im slightly confused by this, why nest them all weird?

[tj]

hmm im slightly confused by this, why nest them all weird?

[secretrobotron]

I'm just trying to automate our documentation system a little bit. Knowing what's parented by what else, I can structure documentation output (html or something) in such a way that member functions can be nested inside classes, etc.

Is there another way to accomplish this? I did write this in the morning...

[secretrobotron]

I'm just trying to automate our documentation system a little bit. Knowing what's parented by what else, I can structure documentation output (html or something) in such a way that member functions can be nested inside classes, etc.

Is there another way to accomplish this? I did write this in the morning...

[tj]

I just haven't seen them nested like that, maybe it's best in a fork of dox

[tj]

I just haven't seen them nested like that, maybe it's best in a fork of dox

[secretrobotron]

Which part is confusing though? Nesting like https://github.com/visionmedia/dox/pull/73/files#L2R27 ?

[secretrobotron]

Which part is confusing though? Nesting like https://github.com/visionmedia/dox/pull/73/files#L2R27 ?

[evindor]

Outdated, sorry.

[evindor]

Outdated, sorry.