Just a quick head's up, we're about to proceed with the renaming of all .c files to .cpp. Nathan is working on updating Makefiles &tc. presently and if it works out, he'll be committing the changes soon.
The expected near-term effects to be aware of:
* Change histories on code files will be reset * Potential build issues on some platforms * Everyone will need to cvs update -Pd, make distclean, and rebuild * Compilation with gcc will cease to work as support for gcc is ended * If you are working on a branch or out of sync with CVS HEAD, your next merge may be more complicated than usual due to the file rename
These issues should be transitory, but please expect some turbulence for a bit.
Thanks, Bryce
Bryce Harrington wrote:
Just a quick head's up, we're about to proceed with the renaming of all .c files to .cpp. Nathan is working on updating Makefiles &tc. presently and if it works out, he'll be committing the changes soon.
The expected near-term effects to be aware of:
- Change histories on code files will be reset
- Potential build issues on some platforms
- Everyone will need to cvs update -Pd, make distclean, and rebuild
- Compilation with gcc will cease to work as support for gcc is ended
- If you are working on a branch or out of sync with CVS HEAD, your next merge may be more complicated than usual due to the file rename
Sounds good.
I assume that this includes all the cleaning up & shortenting of names of the files so that we dont have to rename again.
On Fri, 12 Dec 2003, Jon A. Cruz wrote:
Bryce Harrington wrote:
Just a quick head's up, we're about to proceed with the renaming of all .c files to .cpp. Nathan is working on updating Makefiles &tc. presently and if it works out, he'll be committing the changes soon.
The expected near-term effects to be aware of:
- Change histories on code files will be reset
- Potential build issues on some platforms
- Everyone will need to cvs update -Pd, make distclean, and rebuild
- Compilation with gcc will cease to work as support for gcc is ended
- If you are working on a branch or out of sync with CVS HEAD, your next merge may be more complicated than usual due to the file rename
Sounds good.
I assume that this includes all the cleaning up & shortenting of names of the files so that we dont have to rename again.
That will be part of the work we do for 0.37, yes. This immediate refactoring is literally just .c -> .cpp though.
I think additional planning is needed before we tackle the renaming. For example, we may want to move the sp-* files into a new subdirectory, but will need to discuss that.
Bryce
participants (2)
-
Bryce Harrington -
Jon A. Cruz