Well, yes and no. Yes, when I added up all the errors reported from each of the separate projects that I was trying to build, the total was somewhere over 950,000. However, that does include lots of duplicate errors (for example, from one header that had several errors, and that header was included over and over again), cascading errors (the parser choked on a line, causing it to get confused by the subsequent correct lines of code and thus report lots of bogus errors) and other sundry items that inflated the error count.
So, we didn’t actually have to make 1 million edits to the Office source code, but we did have to slog through a lot of output to clean things up. Including fixing lots of the warnings…
And no, I certainly didn’t do it all by myself. We have a great team of developers at MacBU who collectively tackled this transition. I’ve just been the point man. This long process has been very interesting and I’ve seen a lot of code I’d never looked at before, but I’m ready for us to complete the switch so I can get back to coding real features.
Perhaps tomorrow I’ll discuss the joys of assembly code in a multi-architecture world…
2 replies on “A million errors? Really?”
This must be the second (at least) dev environment transition for Mac Office–do you know anything about the first? I imagine it would have been from MPW, and taken place a long time ago!
I’m not sure wether the world wants to know about ASSEMBLY code in OFFICE…
Perhaps you should write about choosing the wrong tools 🙂