Compilation error are better: if there is a known problem why wait to runtime to error? what's the gain?
Yaron 2013/10/5 Howard Hinnant <[email protected]> > On Sep 21, 2013, at 4:08 PM, G M <[email protected]> wrote: > > > Slight revision to prior chrono patch: Added _LIBCPP_NORETURN. > > (Note dependant upon #warning patch presented previously). > > <chrono.cpp.diff>_______________________________________________ > > cfe-commits mailing list > > [email protected] > > 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. > > Howard > > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
