4 ms·
I would start by getting the code to compile with g++, then begin migrating the dangerous C constructs to safe C++ constructs. IMO, that would be a safe, reason
by w8rbt 10y ago
I would start by getting the code to compile with g++, then begin migrating the dangerous C constructs to safe C++ constructs. IMO, that would be a safe, reasonable thing to do.
- pjmlp 10y agoHow would you prevent other developers to write C style code?
- blub 10y agoProject leadership, coding standards, automated analysis and code reviews. But realistically speaking it might be easier to change tools for a significant number of teams, because the software development community is in general poor at leadership and process. A rewrite seems more approachable for the average (not necessarily average skills-wise) dev compared to a change in attitude, self-reflection and incremental improvement at a department or company level. Then the rust compiler will pummel everyone into submission. This can be a succesful strategy. :)
- pjmlp 10y agoWhich I seldom see in enterprise projects, specially in companies whose business is unrelated to software development and IT is nothing else than a cost center. Anything that is optional gets pushed aside.