Re: Paying developers to get features faster
From: Barry Margolin (barmar_at_alum.mit.edu)
Date: 01/22/04
- Next message: charly: "Re: crack my machine"
- Previous message: Kasper Dupont: "Re: Paying developers to get features faster"
- In reply to: Kasper Dupont: "Re: Paying developers to get features faster"
- Next in thread: Kasper Dupont: "Re: Paying developers to get features faster"
- Reply: Kasper Dupont: "Re: Paying developers to get features faster"
- Reply: Ben Measures: "Re: Paying developers to get features faster"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 22 Jan 2004 07:49:51 GMT
In article <400F7448.E48C741E@daimi.au.dk>,
Kasper Dupont <kasperd@daimi.au.dk> wrote:
> In most cases you can get rid of a warning with just a
> minor code cleanup. There are of course cases, where a
> warning generated for perfectly good code cannot
> easilly be surpressed. For example warning about unused
> function arguments is reasonable, if the argument
> really isn't necesarry, it shouldn't be there at all.
This is all correct. But as I said earlier, these should generally be
infrequent. If the screen is full of warnings, it's unlikely that all
of them are the ones that you can't easily suppress. 1-5 warnings per
program is probably not a big deal, but if there are dozens of them you
should do something about it.
Since we're talking about open source software, it's likely that other
people will be compiling your code when they install it. Lots of
warnings can have an impact on your reputation. And even if you don't
care about that, I expect that many of those users will send bug reports
asking whether the warnings are OK, and you'll have to deal with them.
So taking a little time to get rid of the warnings during development
can have some direct payoff later.
-- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me ***
- Next message: charly: "Re: crack my machine"
- Previous message: Kasper Dupont: "Re: Paying developers to get features faster"
- In reply to: Kasper Dupont: "Re: Paying developers to get features faster"
- Next in thread: Kasper Dupont: "Re: Paying developers to get features faster"
- Reply: Kasper Dupont: "Re: Paying developers to get features faster"
- Reply: Ben Measures: "Re: Paying developers to get features faster"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|