Hi JP, see latest code that chris pushed
On Sat, Jan 7, 2017 at 7:43 AM, jp charras <[email protected]> wrote: > Le 06/01/2017 à 14:35, Simon Richter a écrit : >> Hi, >> >> On 06.01.2017 03:19, Simon Wells wrote: >> >>> converting the std::chrono::system_clock::now() to >>> high_resolution_clock breaks builds on osx, i can't see if there is an >>> explicit conversion function..... is there any reason we aren't just >>> using std::chrono::high_resolution_clock::now()? as this builds fine >>> on osx and i don't really want to have to ifdef it >> >> Yes, that is actually correct. >> >> Another case of gcc accepting incorrect code. :/ >> >> Simon >> > > Hi Simon, > > I don't really understand your answer. > What code is correct and what code is incorrect? > gcc has nothing to do with this issue. > > -- > Jean-Pierre CHARRAS > > _______________________________________________ > 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
