You are more than welcome to take up that call to arms of gcc behavior ;), I am not sure I care that much.... Your suggestion was pointed out and dismissed by people on the gcc alias archive that I read, or to be more specific, patches were possibly maybe being accepted for the issue.
It sure looked like to me that it was a bit of a glibc pointing fingers at the gcc implementation and gcc pointing fingers at the glibc implementation, with a bit of not in my backyard thrown in for good measure. All I wanted to do was to get the code compiling again without me having to go back and make modifications to the bgp_dump.c code to actually handle the write and I wanted enough of a pointer to the issue at hand that someone who might be interested could take up the issue if they so desired. donald On Mon, Oct 12, 2015 at 12:01 PM, Greg Troxel <[email protected]> wrote: > > Donald Sharp <[email protected]> writes: > > > I agree with your sentiments.... I attempted to cover the arguments from > > both sides of the issue in the code comment. I thought about including > > url's but there is no guarantee the pages I used would stay around for > the > > forseeable future. > > What I didn't say so coherently is two orthogonal thoughts: > > If gcc is giving warnings about valid code (casting write to void > counts as valid in my book), then perhaps it is gcc that should be > fixed, not quagga. Debian could patch gcc to turn off this > particular warning. > > Rather than casting away write return values, we could actually check > the return values and log errors, etc. > > > > >
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
