ken.martin at kitware.com
Mon Sep 10 13:27:40 EDT 2018
So... I am seeing lots of warning suddenly pop up on eeloo. As we clearly
want to keep our buildbots green, so that people notice when they introduce
new warnings or errors, these need to be either
1) promptly fixed
or if no one is opting for (1) then
2) suppressed until such as time that someone can fix them
Is anyone doing (1) ? If not then we need to do option (2) or some other
creative idea ...
On Thu, Sep 6, 2018 at 9:08 AM, Ben Boeckel <ben.boeckel at kitware.com> wrote:
> On Tue, Jul 03, 2018 at 12:48:23 -0400, Ken Martin wrote:
> > I think that is a crazy warning gcc is producing and we should disable
> > Way too many false positives with their approach. Can you change the
> > compile flags on eeloo to remove that warning?
> It's not a crazy warning. I saw warnings from the Catalyst builds after
> updating `megas`. The one in vtkObjectFactory is a false positive, but
> rewriting it to use `std::string` instead of `strncat` just makes the
> code easier to read anyways. Errors in pv-forward.c.in were real and
> (since it is C), `snprintf` is the better solution there.
> Basically, `strncat` is a function that is really easy to screw up. We
> really shouldn't use it in C code and certainly not at all in C++ code.
Ken Martin PhD
101 East Weaver Street
Carrboro, North Carolina
This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee. Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers