Re: lintian -- detecting hundrets of bugs within seconds...
- To: firstname.lastname@example.org
- Subject: Re: lintian -- detecting hundrets of bugs within seconds...
- From: email@example.com (Richard Braakman)
- Date: Wed, 28 Jan 1998 14:02:13 +0100 (CET)
- Message-id: <m0xxX8B-001NHbC@night>
- In-reply-to: <19980127155802.27006@kite> from Joey Hess at "Jan 27, 98 03:58:02 pm"
Joey Hess wrote:
> I think it'd be useful to include in the output a reference to the
> appropriate section of the policy manaul. This makes it easy to go read the
> policy, without a long explination. (Also, lose the '-'s, they make it hard
> to read!)
That was part of the plan :-) What you're seeing is the bare-bones
output. "True" lintian will have a postprocessor that adds
explanatory notes to the messages, and refers to the appropriate
documents. (Unless you tell it to be brief, I guess. Flags! Options!)
That's also the reason for the '-'s, the "tag" that will be used to
look up these notes is delimited by spaces. I guess we could use
another delimiter, like :. But would it become any prettier?
> BTW, I was earlier looking into making the policy manual a literate
> programming document that generated a lint checker and the policy manual. I
> never got very far with it, but I wonder if you've givn any thought to that?
Ooh wow. This is the first time I saw an application for literate
programming and thought "yeah, that's useful". (Normally I view it as
an excellent way to lose your code among mountains of explanations.)
Still, it's something to consider when lintian has matured, not before.
Right now the focus is on writing it.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .