At 11:05 +0200 30 Mar 2000, Thomas Roessler <[EMAIL PROTECTED]> wrote:
> On 2000-03-30 09:14:09 +0100, Chris Green wrote:
>
> > There a couple of compiler warnings:-
> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl -I../intl -Wall -pedantic -g
>-O2 -c imap.c
> > imap.c: In function `imap_check_mailbox':
> > imap.c:1157: warning: `t' might be used uninitialized in this function
>
> This is an over-eager gcc. The variable is not used
> uninitialized.
Still, it would probably be a good idea to prevent the warning.
Spurious warnings can mask ones that are real problems.
> > fac that the install tries to set mutt_dotlock's
> > permissions even though I have done a local directory
> > install.
>
> umh... I wouldn't really consider this a problem in the
> installation mechanism...
Since in cases like this, the resulting install could easily be unsafe,
it could be argued that installing at all is an error. There should
probably be more noticeable errors at the least, maybe even require the
person doing the install run something like "make unsafe_install".
--
Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/
Everyone can be taught to sculpt: Michelangelo would have had to be
taught how _not_ to. So it is with the great programmers.
