Received: by 10.42.155.2 with SMTP id s2mr34947383icw.5.1320589739041;
        Sun, 06 Nov 2011 06:28:59 -0800 (PST)
Path: h5ni5034pba.0!nntp.google.com!news1.google.com!news.glorb.com!aioe.org!.POSTED!not-for-mail
From: dpb <n...@non.net>
Newsgroups: openwatcom.users.fortran
Subject: Re: BTW, what's the /c for -- Re: Did the E3033 problem get resolved?
Date: Sun, 06 Nov 2011 09:28:47 -0500
Organization: Aioe.org NNTP Server
Lines: 61
Message-ID: <j965j2$sh8$1@speranza.aioe.org>
References: <j8vs0h$98o$2@dont-email.me> <4EB40773.CD3D6908@alum.mit.edu> <j928e1$uki$2@dont-email.me> <j93ttv$dl9$1@www.openwatcom.org> <j93vla$t3v$1@speranza.aioe.org> <j945k2$oap$1@www.openwatcom.org>
NNTP-Posting-Host: TdgXQfeR03yUk6Cy3FOs4Q.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
X-Notice: Filtered by postfilter v. 0.8.2
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/5/2011 3:17 PM, Lynn McGuire wrote:
...

> Dont know. I'm an old mainframe hacker who moved to
> PrimeOS to Vax to Unix to PC. Except for the PC, I
> always used command lines tools instead of IDEs.
> Nowadays I prefer IDEs but they must work and work
> well. Watcom's IDE does not meet this requirement,
> it is just too simplistic. So we just use the command
> line tools provided by Watcom as they are robust and
> simple.
>
> We use Visual Studio exclusively for our user interface
> (600,000 lines of C++ code) and some days I want to
> throw it out the nearest window. BTW, when I first
> tried to port our F77 code to Intel Fortran, we
> overloaded it's linker internal tables and had to wait
> a couple of months for a patch. Then I ran into their
> zero init bug and gave up in disgust.
...

Pretty similar path from Philco-->CDC Cyber/Star-->DEC 10 -->VAX and 
PDP's of various ilks --> period of embedded systems far removed from 
any Fortran at all -->back to VAX -->PC OS/2 to --> NT4 (first MS OS 
used "in anger")

The code base that got me to the Watcom compiler was moved from VAX to 
OS/2 (Watcom) then to the DVF to move it to NT4.  It doesn't have a user 
interface other than terminal; I wrote a small demo and a proposal to 
build one w/ Tcl/Tk but the client never funded the development.

I didn't do the OS/2 conversion from VAX but picked up a modification 
and support and the move to NT4 (when also moved it from OW as the 
client wanted a commercially supported compiler.  (Of course, that DVF 
morphed to CVF then shortly died is an ironic sidebar.)  It's not as 
large as yours (and I've never counted lines nor routines) but is a 
suite of half-dozen multiple independent executables using shared memory 
and semaphores to monitor plant performance on real time basis using 
interface to plant control system and thermodynamics plant models for 
heat rate, etc., as well as interactive analysis tools and a historian, 
etc., etc., etc.  No IDE here, either, I built onto the existing make 
files and use the JPSoft command interpreters on MS (or used REXX on 
OS/2) to build more sophisticated batch files for the compilation 
process and the configuration management package for source control and 
edit check-in/-out.

I've used the Visual Studio distributed with the DVF/CVF distribution 
some for small projects or playing around but don't believe I would ever 
willingly go that route on anything large; I can't stand the editor 
limitations/idiosyncracies (vis a vis the different idiosynracies that I 
_am_ used to :) ).

We've had at the Intel zero-init thing re: your code and the other 
extensions used that aren't supported by other potential choices 
otherwise ad nauseum in the past; I retired from active consulting not 
too long after the time Intel bought the compiler group from Compaq and 
the aforementioned project wasn't funded to provide any revenue so I've 
never updated either Fortran/C compilers nor Matlab license since ...and 
at this point don't expect to.

--