Developers: Clear Your Regression/Inspection Failures
Okay, I've been keeping quiet because I had too many of these myself, but I'm now getting close to having clean reports so I feel entitled to harass the rest of you ;-} So I'm going to say the obvious: it's high time we got 1.34 out the door. Devote a few hours a week to clearing away the problems for which you are responsible, and we'll be there in short order. If there are any obstacles standing between you and steady progress towards a clean report, please let our release manager (Thomas Witt) know. Thanks for your attention, Dave -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
Okay, I've been keeping quiet because I had too many of these myself, but I'm now getting close to having clean reports so I feel entitled to harass the rest of you ;-}
So I'm going to say the obvious: it's high time we got 1.34 out the door. Devote a few hours a week to clearing away the problems for which you are responsible, and we'll be there in short order.
I agree it is time to get this out the door. When I look at my report for, say, ptr_container it is: |ptr_container| libs/ptr_container/doc/tutorial_example.html: *A* unlinked file Whether or not the file is linked, it might still be used if it is included verbatim into another file. So it a bit irritating that we get this in our face. How do you turn off that message? -Thorsten
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
When I look at my report for, say, ptr_container it is:
|ptr_container| libs/ptr_container/doc/tutorial_example.html: *A* unlinked file
Whether or not the file is linked, it might still be used if it is included verbatim into another file.
So it a bit irritating that we get this in our face. How do you turn off that message?
There's some kind of directive you can put in the file, but AFAICT the directives aren't documented. Rene, can you write something up... or suggest someone to do it? Actually, maybe in this case the inspection tool should account for verbatim includes... I didn't know that you could do that with HTML, though. Howzat work? Thanks, -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
t a bit irritating that we get this in our face. How do you turn off that message?
There's some kind of directive you can put in the file, but AFAICT the directives aren't documented. Rene, can you write something up... or suggest someone to do it?
Actually, maybe in this case the inspection tool should account for verbatim includes... I didn't know that you could do that with HTML, though. Howzat work?
In rst-files you can include html files. If this file is actually included or not, I can't remember, but I don't mind it being there for now. So it would be good to be able to disable the warning. -Thorsten
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
David Abrahams wrote:
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
t a bit irritating that we get this in our face. How do you turn off that message?
There's some kind of directive you can put in the file, but AFAICT the directives aren't documented. Rene, can you write something up... or suggest someone to do it?
Actually, maybe in this case the inspection tool should account for verbatim includes... I didn't know that you could do that with HTML, though. Howzat work?
In rst-files you can include html files. If this file is actually included or not, I can't remember, but I don't mind it being there for now. So it would be good to be able to disable the warning.
IME it's much easier just to put the license/copyright info in an HTML comment and be done. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
In rst-files you can include html files. If this file is actually included or not, I can't remember, but I don't mind it being there for now. So it would be good to be able to disable the warning.
IME it's much easier just to put the license/copyright info in an HTML comment and be done.
well, but how do you remove the complaint about the file being unlinked? -Thorsten
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
David Abrahams wrote:
Thorsten Ottosen <thorsten.ottosen@dezide.com> writes:
In rst-files you can include html files. If this file is actually included or not, I can't remember, but I don't mind it being there for now. So it would be good to be able to disable the warning.
IME it's much easier just to put the license/copyright info in an HTML comment and be done.
well, but how do you remove the complaint about the file being unlinked?
Insert boostinspect:nounlinked in a comment, I think. -- Dave Abrahams Boost Consulting www.boost-consulting.com
Thorsten Ottosen wrote:
In rst-files you can include html files. If this file is actually included or not, I can't remember, but I don't mind it being there for now. So it would be good to be able to disable the warning.
Right now there isn't, so I've had a quick go at adding one. With this change, you can add a comment containing 'boostinspect:unlinked' to disable the check. It would be better to scan rst files, but I think that's probably more trouble than it's worth. Please can someone who knows inspect take a look at the patch? Daniel
participants (3)
-
Daniel James -
David Abrahams -
Thorsten Ottosen