kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

+1 for typing out the first definition.

In functions, I'd be in favor of using 'auto' and 'decltype' when 
declaring local variables that need to match the class variable.

Best-
Seth

On 2019-08-08 02:43, Jeff Young wrote:
> When I worked at Frame a colleague advised me not to create Framegol.
> (That was back in the day when Pascal and C were considered Algol
> family languages.)  I’ve always taken that to heart and so prefer
> std::shared_ptr<TYPE>, ugly as it is.
>
> Cheers,
> Jeff.
>
> > On 7 Aug 2019, at 23:18, Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx> 
> > wrote:
> >
> > Hi Fellow Devs,
> >
> > I'm fixing some memory management issues in the P&S by introducing 
> > smart
> > pointers here and there. Do we have any coding policy on typedefing
> > shared_ptrs/unique_ptrs?
> >
> > Should I:
> > - always use std::shared_ptr<TYPE> explicitly?
> > - or am I allowed to typedef std::shared_ptr<TYPE> TYPE_SP (or 
> > something
> > alike)?
> >
> > Cheers,
> > Tom
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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