legacy

For legacy reasons, I'm using CVS on a project. Recently I committed some changes which broke our code and I needed to revert them. What's CVS's analog of git revert -r <old_revision> ? Looking at past questions like How to revert big change , CVS commits don't group the files that were changed. Is the only way to revert by using dates? Also, what's the best way to view past changes? CVS log outputs too much info, most of which is unnecessary. I want to see commit messages and changed files. CVS documentation can be found here , but from this site it tells how to revert a single file: MAKING

I'm currently in a project which develops using a framework developed by another department as the base. We are currently introducing quality standards (at last, yay!) in our department, but it's currently impossible to introduce those to the other department. As a consequence, we are working against a constant moving target without either API stability or stable releases, which is stressful at the very least. Since we are trying to fix things at our end first, we'd like to secure ourselves as far as it gets against changes in the "upstream" a.k.a. framework code. We'd envisioned hard module

My department is currently faced with the responsibility for the task of maintaining a rather large COBOL code base. We are wondering how to add new features to keep up with business needs. COBOL programmers are hard to come by these days, and we also think we would get higher productivity from using a more modern language like Java or C#. We feel that we have four options: Rewrite everything from scratch, leaving the old application to itself until it is ready to be replaced Rewrite everything from scratch, getting some people to maintain the old application to cope with new business needs as

We have a situation at work where developers working on a legacy (core) system are being pressured into using GOTO statements when adding new features into existing code that is already infected with spaghetti code. Now, I understand there may be arguments for using 'just one little GOTO' instead of spending the time on refactoring to a more maintainable solution. The issue is, this isolated 'just one little GOTO' isn't so isolated. At least once every week or so there is a new 'one little GOTO' to add. This codebase is already a horror to work with due to code dating back to or before 1984

Joining an existing team with a large codebase already in place can be daunting. What's the best approach; Broad; try to get a general overview of how everything links together, from the code Narrow; focus on small sections of code at a time, understanding how they work fully Pick a feature to develop and learn as you go along Try to gain insight from class diagrams and uml, if available (and up to date) Something else entirely? I'm working on what is currently an approx 20k line C++ app & library (Edit: small in the grand scheme of things!). In industry I imagine you'd get an introduction by

I have inherited some Classic ASP code and I need a JSON library that can be instantiated and run server-side for use with JavaScript-coded server-side ASP. How can I do this? Jørn Schou-Rode For writing/outputting JSON i believe the aspjson project is a pretty good choice. Parsing JSON in ASP "classic" is discussed here: Any good libraries for parsing JSON in Classic ASP? In that thread, Chris Nielsen has a creative idea of using a Javascript library on the server side (as ASP supports JScript as well as VBScript). I have not tried it, but maybe that could solve both parsing and writing. In

Is there any good library for reading / writing DBF files in java or any other language ? You might give this library a try: http://dans-dbf-lib.sourceforge.net/ It is open source (GPL) and pure Java. Its easy to get to via OleDB provider, such as via .Net, Visual Foxpro would obviously be able to read it natively. A quick google for dbase and jdbc brought back a number of links for an xbase jdbc driver called StelsDBF. Can't say I've used it or know more than a quick google, but that would be my Java answer. An alternative Java solution would be to set up an ODBC data source for dbase and

We're having problem with a huge number of legacy stored procedures at work. Do you guys recommend any tool the can help better understand those procedures? Some kind of reverse engineering that indentifies inter-procedure dependencies and/or procedure vs. tables dependencies. Can be a free or commercial tool. Thanks! rpetrich Redgate has a rather expensive product called SQL Dependency Tracker that seems to fulfill the requirements. ConcernedOfTunbridgeWells The cheaper solution than 'dependency tracker' is the data dictionary table sys.sql_dependencies which from which this data can be