I recall a project where we created a codegenerator from the COBOL object definitions.
It basically created boiler plate code that could read and write the data in the format that COBOL dictated. It also created c# classes from those definitions, that were actually usable in the .net world. The layout in memory was not the same as the COBOL object definition. I know COBOL can define fields over field boundaries, but I dont recall if our generator supported that. I have to lookup the sources (if possible...) to give you more detailed information. // Ryan On 11/14/06, Jon Rothlander <[EMAIL PROTECTED]> wrote:
I just wanted to point out the reason we are doing this because a number of post have suggest not try this at all. Here's the basic reasoning behind attempting to this and not just wanting to rewrite it. The options for the client are really pretty simple. If there is no solution in .Net, the client will simply throw out .Net as a solution, as .Net doesn't look like it can handle this. They would have the option of working with other .Net languages such as COBOL for .Net, which kind of destroy the whole point of moving to .Net in my opinion. So I find it hard to recommend that to a client. The odd thing here is that this is being done in Java without any issues... or at least the issues where not big enough to throw out the solution. So in my opinion the client would simply choose Java over .Net since .Net cannot handle this. The estimates that we are coming up with are about $20M to rewrite and about $300K to $600K to migrate the code in Java. So it would be hard for a $10M company to pick .Net over Java with the price tag of $20M compared to $600K. No matter how many points we give them in regards to how .Net compares to Java, the price tag along will kill it. I don't know how Java is able to do this, but it does. There are legacy tools to translate this code into Java... and they work. Whatever solution the Java tools are using would seem to be something I could use in .Net. Maybe that's the direction I should go with this. De-engineer a Java solution. =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
=================================== This list is hosted by DevelopMentorĀ® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com