-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jon S. Berndt schrieb: > If cost is an issue (isn't it always?), is it worth > it to expend the resources to clean up code that may have been gathering > flotsam and jetsam for years - particularly if you want to add some new > features (base on new requirements), anyhow?
I'm sure you know the "never change a running system". This is IMHO responsible for the many old fashioned Fortan stuff that's still used today (although modern C++ would give better performance, etc. pp.) On the other hand at my day job the embedded software development team next to me does change languages (from hand coded C to ASCET to TargetLink to Simulink Embedded Coder) - but that's a slow process and only parts that need a redesign are affected. The parts that need only minor additions will stay in the same language unless there's a big need to. So what would I do in your case (except that I don't know it ;): Stay with the C code, write unit tests that cover the interface of the C modules (anyway a good idea) and then switch to C++ module by module when that module needs a major change. Use the unit tests to make sure the C++ behaves the same as the C. Sometime inbetween you might change from C with C++ moduled over to the C++ with C modules (what I guess would be the major benefit by that language change). CU, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREIAAYFAkyTqdwACgkQoWM1JLkHou3aZACgjP4tIAno2/KyuNMSUXdksd9I HNAAn2+FhLzf7mTaM+swWH+0Ubu5BnDx =eBIT -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
