In large C++ projects (take Firefox as an example), it's actually the other
way around: merging a lot of .cpp files to compile larger but fewer
translation units gives you *much* faster builds (and better optimization,
at least without LTO).
My advice is to split your (large) program into a few
This is great, thanks!
On Thu, Apr 17, 2014 at 9:21 AM, Flaper87 flape...@gmail.com wrote:
2014-04-17 2:11 GMT+02:00 Alex Crichton a...@crichton.co:
The template which breaking changes will be required to look like is:
First, a brief one-line summary of the change
Second,
I don't want to discourage English speakers so I think we should do it in
English and optionally switch to French depending on the audience. I have
been to a few hacker meetups in Paris where the language of choice for
presentations was English (even though 90% of the attendees were French)
and it
I ran into a similar situation in my own code and did something which would
transpose to:
type WindowFlags = u32;
static SDL_WINDOW_FULLSCREEN : u32 = ffi::video::SDL_WINDOW_FULLSCREEN;
...
I think enums are not a good fit for bitwise operations, it's not really
meant for that.
Cheers,
Nical
