I presume then that you also feel that allowing bcopy to copy volatile regions is a bad idea?
On Wed, 27 Feb 2002, Peter Wemm wrote: > Alfred Perlstein wrote: > > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > > > : > > > :ok so I leave it to other people to fix LINT > > > :I'm not going near it any more > > > > > > It's the responsibility of whoever added -Werror to the default > > > compile to unbreak the tree, either by fixing the problem or by > > > backing out his commit. > > > > No. Leave it in, this will benifit us all in the long run. > > > > In fact it was the _only_ way I was able to get people clean > > up bad code at a former job and I strongly support keeping > > -Weerror enabled. > > If there are files that are too hard to fix, or vendor files, or the fix > isn't clear, we should use the nowerror conf/files* flags. > > It is important that we stop new warnings turning up when the compile > output is so damn large that it hides things. > > I will do a pass over things now and see what I can do. > > Cheers, > -Peter > -- > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
