Planning new apps to replace our MPE ones that can't
easily be ported or that really do need to be re-written...

One school of thought is that we should write new stuff
in C, avoiding use of the heap and pointers to avoid hard
to find bugs.  C is attractive for attracting new programmers,
but how hard it is for Cobol programmers to learn to use C?
C is also good preparasion for learning Java, but I'm afraid
of Java for performance reasons.

Another school of thought is that the programmers write in
the lanquage they know best, to get the best code with the
highest productivity.  This appeals to me, since productivity
is going to be extemely important.  The some modular design
can be writen in either C or Cobol and as long as the two talk
to each other this multi-lanquage strategy would work.

How well do different lanquages cooperate on Unix or Linus?
(i.e. Can Cobol make libraries C can call, and the reverse?)

Richard
--
Richard L Gambrell, Senior Information Technology Consultant and
Director of Computing Systems and Networks
Information Technology Division, University of Tennessee at Chattanooga
Fax: 423-755-4150                Support Help-Desk: 423-755-4000
Direct phone: 423-755-5316       ITD Business Office: 423-757-1755
Mobile (urgent): 423-432-5122    Main UTC: 423-755-4111
Email: [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *