More details on warnings?

45 views
Skip to first unread message

Raymond Camden

unread,
Apr 23, 2014, 11:38:39 AM4/23/14
to appl...@googlegroups.com
I'm running appledoc against multiple different folders. I get warnings that are a bit vague:

WARN | foo is not documented!

Sometimes it is easy to tell where foo is coming from, but it always isn't obvious. Is there an option to make it more verbose? I..e,

WARN | foo is not documented! (projectX/foo.h)

Rob Van der Veer

unread,
Apr 23, 2014, 11:41:11 AM4/23/14
to appledoc on behalf of Raymond Camden
Sounds like a feasible option.

--
You received this message because you are subscribed to the Google Groups "appledoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appledoc+u...@googlegroups.com.
To post to this group, send email to appl...@googlegroups.com.
Visit this group at http://groups.google.com/group/appledoc.
For more options, visit https://groups.google.com/d/optout.

Raymond Camden

unread,
Apr 23, 2014, 11:43:48 AM4/23/14
to appl...@googlegroups.com
I *did* find the verbose option, but, afaik, it doesn't show this. It got VERY verbose at higher levels so it is possible I missed it, but it seems to me that the warnings should include the filename by default. It is a tiny bit more text so even at the default verbosity level it should be there (imo).


On Wednesday, April 23, 2014 10:41:11 AM UTC-5, Rob Van der Veer wrote:
Sounds like a feasible option.

Tom @ Gentle Bytes

unread,
Apr 23, 2014, 11:48:44 AM4/23/14
to appledoc on behalf of Raymond Camden

Did you try with --logformat xcode - this should include full path to the file as well as line number?

On 23 Apr 2014, at 17:43, Raymond Camden via appledoc wrote:

I did find the verbose option, but, afaik, it doesn't show this. It got


VERY verbose at higher levels so it is possible I missed it, but it seems
to me that the warnings should include the filename by default. It is a
tiny bit more text so even at the default verbosity level it should be
there (imo).

On Wednesday, April 23, 2014 10:41:11 AM UTC-5, Rob Van der Veer wrote:

Sounds like a feasible option.

www.simplicate.info

On Wed, Apr 23, 2014 at 5:38 PM, Raymond Camden via appledoc <

Raymond Camden

unread,
Apr 23, 2014, 11:49:30 AM4/23/14
to appledoc on behalf of Tom
Wow - that is *exactly* what I wanted. Thank you!


--
You received this message because you are subscribed to a topic in the Google Groups "appledoc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/appledoc/c4IqPQC1pJM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to appledoc+u...@googlegroups.com.

To post to this group, send email to appl...@googlegroups.com.
Visit this group at http://groups.google.com/group/appledoc.
For more options, visit https://groups.google.com/d/optout.



--
===========================================================================
Raymond Camden, Web Developer for Adobe

Email : raymon...@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden

Rob Van der Veer

unread,
Apr 23, 2014, 11:49:47 AM4/23/14
to appledoc on behalf of Raymond Camden
When run from XCode, the logs shouldn't include the obvious location as the IDE already takes care of that.. My 2c,

Tom @ Gentle Bytes

unread,
Apr 23, 2014, 11:53:29 AM4/23/14
to appledoc on behalf of Rob Van der Veer
You mean project root folder part of path?

Full path was required in order for Xcode to pick it up at the time I
implemented the option. It's possible clang can handle paths relative to
project root nowadays, didn't try it... Would certainly make ouput nicer
though, I agree.

Tom @ Gentle Bytes

unread,
Apr 23, 2014, 11:53:34 AM4/23/14
to appledoc on behalf of Raymond Camden

Cool!

On 23 Apr 2014, at 17:49, appledoc on behalf of Raymond Camden wrote:

Wow - that is exactly what I wanted. Thank you!

Reply all
Reply to author
Forward
0 new messages