All commits I made after forking.

[CarloWood]

I can imagine you don't want the 'remove generated files' commit - although I consider it very bad practice to put generated files in a git repository; I had to re-run aclocal -m m4; autoheader; autoconf; automake --missing --foreign anyway because you used am version 1.14 to generate these files, which I don't have installed; which breaks building.

Removing 'using namespace std' and using the correct standard header names are just good C++ practice. You should probably merge those. The compiler warning thing is just a warning, but compiler warnings are annoying. Finally, if you'd be so kind to consider adding cwm4 support then I don't need to keep my own fork ;). This just adds a file configure.m4 which then allows fully automatic integration with other projects (that use cwm4) as git submodule (no configuration or editing of build system files required: just a git submodule add ... and done).

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[googlebot]

CLAs look good, thanks!