This question already has an answer here:
I'm working on a large codebase whose core modules are in C and extension modules are in C++. We have a coding convention for C code but I'm being told that we need to enforce the same coding convention for C++ modules.
As a personal preference I dislike using an ANSI-C style declaring variabile at the beginning of the scope instead at the first point of use (that forces me to navigate backward each time to see what a variable type is and I think it's also way more error-prone since you forget variables if the function has many) and I also dislike not being able to use smart pointers and deallocating lots of things in a non-RAII fashion if an error comes up.
My boss says that style consistency matters more than anything else but we disagree on this point (if we have the tools to render our C++ modules more clear and readable ~ thus maintainable.. why not using them?).
Is this common in a large mixed C/C++ project?