|
Douglas Handy wrote: > > Pat/Booth, > > >you could then begin to migrate out of the S/36EE to full native... This > >method requires nothing more than a recompile... > > Maybe, maybe not. Restoring to the *M36 is a pretty fail-safe > operation since everything is guaranteed to work just as before, only > faster. The *M36 is object code compatible with the S/36. > > But moving to the S36EE is a migration process that may or may not be > smooth and easy, depending on the applications. I worded that badly, but meant to say, that moving from M36 to S36EE "should" be fairly easy, with the recompile being the biggest problem.... There are some very minor changes, but for the most part, 98% goes across with little or no problems... The things that you mentioned are valid points but could be worked around with out too much hand wringing..... Lack of source is another whole problem..... +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.