HP3000-L Archives

October 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Walter Murray <[log in to unmask]>
Reply To:
Walter Murray <[log in to unmask]>
Date:
Fri, 12 Oct 2001 19:16:21 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
"Mark Boyd" <[log in to unmask]> wrote in message
news:9q78hs027gv@enews4.newsguy.com...
> We just received the excerpt below from our software vendor.  Is anyone
> familiar with what problems *Might* arise by co-mingling 6.0 and 6.5
object
> generated by the Cobol compiler?

[snip]

Your software vendor may be referring to the problems I discussed in my 6.5
Communicator article, "Compatibility Considerations for COBOL and C."  In a
nutshell, if you compile code on 6.5 and then try to link it or add it to an
XL on 6.0, you could have problems.  The COBOL II/iX compiler on 6.5 was
updated to make use of new millicode routines for more efficient 64-bit
arithmetic, and those routines aren't present in the millicode library on
6.0.

But that shouldn't cause a problem when moving forward.  I don't know of any
scenario where COBOL code compiled on 6.0 can't be brought forward and mixed
with code compiled on 6.5.

Walter Murray
Hewlett-Packard
COBOL II/iX project

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

ATOM RSS1 RSS2