Attendance
I have come to realize that I hadn't picked a good naming convention for the functions we have created so far. We could live with it, but I'm inclined to fix the problem instead.
I have just made a change to the CVS archive. DO NOT MAKE ANY FURTHER CHANGES TO ANY FILES WITHOUT FIRST FOLLOWING THE INSTRUCTIONS BELOW.
Login to the system where you do your CVS work. If you have two systems where you do this, you will need to do these steps on each of them. The commands must be typed exactly as shown (or better yet, cut and paste).
cd System
for f in test/cn_*; do
n=test/cn_in_${f##test/cn_}
echo $f
mv $f $n
done
for f in src/cn_*; do
if [ -n "${f##src/cn_defines.h*}" \
-a -n "${f##src/cn_types.h*}" \
-a -n "${f##src/cn_charClassifier*}" ]; then
n=src/cn_in_${f##src/cn_}
echo $f
mv $f $n
fi
done
The commands above should not result in any error messages. If there are errors, do not proceed, but report the errors to me and to Gary.
What you have done so far is to rename your existing files into the new naming convention. If you are sure there is nothing uncommitted in your files you can skip the steps above and instead do the following:
rm src/cn_* test/cn_*
Once those steps are done, you then need to update your local CVS sandbox. That is done as shown here:
cd ..
cvs checkout -R System
You will now be free to make edits as before. The first thing that needs to be done is to change the function names to match the new file names. Go for it.
After making the renaming change above I fixed cn_in_command(). But in so doing, I needed to change a bunch of other functions. So now most of them are name clean except that their test files have not yet been patched.