Oh, I missed that. That's totally the approach I would take, and I don't really see it as a problem to use a separate channel to document the documentation functions/macros. It seems like a messiness related more to bootstrapping (documenting using the system you're writing) rather than a design problem.
I guess the need to document @doc goes away if it become the keyword doc, since you would need some separate way to document keywords (if you were going to do that) anyway. -- Leah On Thu, Sep 11, 2014 at 4:58 PM, Michael Hatherly <[email protected] > wrote: > I'm doing it using an internal macro `@docref` [1] to track the line > number and then in `src/doc.jl` I store the documentation in `__METADATA__` > along with the line and source file found using `@docref`. A bit hacky, but > it's only for a couple of docs. > > [1] > https://github.com/MichaelHatherly/Docile.jl/blob/c82675d4a39932d1d378e954844018cefc091858/src/Docile.jl#L14-L17 >
