Dann Corbit wrote: > I am not enrolled in the CVS project, and don't even know how to use it. > We use "Visual Source Safe" here -- really an icky tool but at least > everyone here knows it.
Source Safe? Yikes. I haven't used that in a long time. > > There is some debate here as to whether to keep the changes private or > to turn them back to the project. Not sure how it will turn out. > > I am not sure that the project would want them anyway, since the > represent some pretty major surgery and impact the readability of the > code in a quite adverse way. I hear you on that. I have tons of code that has #ifdef GCC and #ifdef WIN32 in lots of places. Obviously you wrap what you can in macros and/or functions, but you can't do that 100% the time. Some people REALLY hate #ifdef/#endif and view them as a bad coding practice. Others, like myself, view them as a proper usage of the language constructs and judicious use of them actually help the developer understand the code better. > > At any rate, the Japanese version appears to be released. In fact, I > have downloaded the whole project and gave it a spin. It is actually > very nice. If you just need to use something for right now, why not go > with that version? I have no desire for a Windows version for myself, but I see the need for it. > > In any case, there is simply no way possible that anything will ever > escape from here before June at the absolute earliest (full regression > test is company policy). ok ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
