Ah portability, the ultimate panacea... I was involved in a project in the past where we were told, oh don't worry, the product is portable, it is written in "c". So I asked how long it would take to get it to run on Windows (it was written for Solaris) and I was told, 6-8 weeks. I said well, if it is "portable" shouldn't it just be a tweak of the make file, and a re-compile? 10 weeks later, I looked at the code, and there were almost as many #if defined(WIN32) #elseif defined(SOLARIS) than lines of c code. Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Thursday, May 31, 2007 12:31 PM To: [email protected] Subject: Re: Cross-assembler : HLASM --> 8086 On Thu, 31 May 2007 13:38:16 +0100, Flint, Mike wrote: > >Does anyone know of a product that will take HLASM source and produce object or executables for the wintel platform? ... >The code is 'pure' HLASM (number-crunching, not accessing any MVS services), so it shouldn't need to handle many environment issues (other than passing parameters in, and getting the response out). > <HERESY>I sense a good argument here for writing non-system-services-dependent code in a language more portable than HLASM.</HERESY> But, I suspect that for you it's water under the bridge. Others take heed. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
