← Back to team overview

kicad-developers team mailing list archive

Re: Static initialization order fiasco

 

On 12 April 2014 13:46, Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx> wrote:
> On Sat, Apr 12, 2014 at 12:56:24PM -0700, Alexander Lunev wrote:
>> As it turned out, the issue is with undefined static initialization order.
>
> Yay for usual C++ sickness on 'obvious' details... IIRC it usually warns
> for these things. Maybe similar ones and not this in particular.
>
> C++ is becoming unmanageable (worse than Java, I'd say)

No, this is just a matter of using the language correctly.

Static initialization for instance should really be used sparsely and
only if you know what you're doing
(not sure it this fits my observations in KiCad code though :) ).

-h

>
> --
> Lorenzo Marcantonio
> Logos Srl
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


Follow ups

References