chrono libcxx msvcrt patch slight revision
yaron.keren at gmail.com
Fri Oct 4 14:26:39 PDT 2013
Compilation error are better: if there is a known problem why wait to
runtime to error? what's the gain?
2013/10/5 Howard Hinnant <howard.hinnant at gmail.com>
> On Sep 21, 2013, at 4:08 PM, G M <gmisocpp at gmail.com> wrote:
> > Slight revision to prior chrono patch: Added _LIBCPP_NORETURN.
> > (Note dependant upon #warning patch presented previously).
> > <chrono.cpp.diff>_______________________________________________
> > cfe-commits mailing list
> > cfe-commits at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
> Question for those interested in libc++ on Windows:
> I generally prefer my errors to come at compile time, or at least link
> time, rather than run time. This patch delays until runtime the fact that
> the chrono clocks are not implemented. Is that really what the Windows
> porters want? If so, I'll commit this patch. I just wanted to ask first,
> as it is not what I did for Apple platforms.
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-commits