Please go ahead, it makes the code hard to read when instancing an object
in the middle of a function causes a global change in the application.
Encoding should be encapsulated in the streams themselves. Without that,
the ugly hack is the only way to make the even uglier global locale setting
hack be exception safe.

On Mon, Jul 17, 2017 at 7:44 PM, Chris Pavlina <[email protected]>
wrote:

> If I somehow found the time to strip LOCALE_IO completely out of the
> footprint parser without changing the behavior, would anyone have any
> religious objections or otherwise mourn the loss?
>
> --
> Chris
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : [email protected]
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Reply via email to