On Fri, 20 Sep 2002, Zane Gilmore wrote:
> This is not because COBOL is the "best" language for the job but because > that's what they've always used. There are heaps of "better" languages. Here's where I agree with Zane...not that that's unusual :) I've actually worked with a couple of companies that use COBOL in various ways (wanganui computer and a Y2K company). Most COBOL programs simply access a database, transform the data and present it to the user or take user's input, transform it, and dump it into the database. Cobol is not the best for this task...IMHO it's much easier to use apache/php3/postgresql (or any other combination of presentation tool, transformation language, and database server). On Fri, 20 Sep 2002, stringer wrote: > My point is that I agree with whoever said that it is the problem you > are trying to solve which will determine the tool you use. hay, that was me...cool :) tim http://www.cosc.canterbury.ac.nz/~tnw13 Quidquid latine dictum sit, altum viditur.
