Re: [Kicad-developers] Coverity heads-up

On 1/12/20 10:36 AM, Jon Evans wrote: > It's worth mentioning that I'm getting rid of PARAM_CFG_ARRAY in my new > settings branch (should be done before FOSDEM) Sounds like this solves half of the problem. > > On Sun, Jan 12, 2020 at 10:31 AM Jeff Young > wrote: > >

Re: [Kicad-developers] Coverity heads-up

It's worth mentioning that I'm getting rid of PARAM_CFG_ARRAY in my new settings branch (should be done before FOSDEM) On Sun, Jan 12, 2020 at 10:31 AM Jeff Young wrote: > Hi Wayne, > > The main one that permeates the code is CONFIG_PARAM_ARRAY. It doesn't > use any of the boost::ptr_array fanc

Re: [Kicad-developers] Coverity heads-up

Hi Wayne, The main one that permeates the code is CONFIG_PARAM_ARRAY. It doesn't use any of the boost::ptr_array fancy stuff. We don’t currently catch /any/ of the exceptions thrown by boost for this data structure, so that part is unchanged. What does change is the signal-to-noise ratio out

Re: [Kicad-developers] Coverity heads-up

Hi Jeff, We should probably discuss this a bit before you spend any time on it. The boost pointer containers do a lot of housekeeping under the hood that the standard c++ containers do not. This means that all of the object cloning behavior automatically handled by the boost pointer containers wi