<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>openwatcom.users.fortran Google Group</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran</link>
  <description>OpenWatcom Fortran Discussion</description>
  <language>en</language>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/ab73468fc698fd7a?show_docid=ab73468fc698fd7a</link>
  <description>
  And we are now rid of all our zero initialization &lt;br&gt; problems. That only took a couple of months ... &lt;br&gt; &lt;p&gt;Lynn
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/ab73468fc698fd7a?show_docid=ab73468fc698fd7a</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Thu, 02 Feb 2012 19:03:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/51e564d4e3c232a6?show_docid=51e564d4e3c232a6</link>
  <description>
  Sorry, I&#39;ve been here before. The decision is &lt;br&gt; made and we are moving out. &lt;br&gt; &lt;p&gt;Lynn
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/51e564d4e3c232a6?show_docid=51e564d4e3c232a6</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Fri, 27 Jan 2012 22:23:20 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/340c5796403c352f?show_docid=340c5796403c352f</link>
  <description>
  My good friend StackWalker has saved our rumps &lt;br&gt; many times ... &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.codeproject.com/Articles/11132/Walking-the-callstack&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;Dont know on the code generator does it yet but &lt;br&gt; I&#39;m sure that we will get burned XXX find out &lt;br&gt; soon. It must be doable because I remember using &lt;br&gt; f2c on our first unix port (now that was nasty
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/340c5796403c352f?show_docid=340c5796403c352f</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Fri, 27 Jan 2012 22:22:19 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/55c913b7a47d3f17?show_docid=55c913b7a47d3f17</link>
  <description>
  ... &lt;br&gt; &lt;p&gt;No argument on the usefulness of a good traceback. &lt;br&gt; &lt;p&gt;I &amp;quot;know nuthink!&amp;quot; (to quote Sgt Schultz) of current MS Visual C/C++ but &lt;br&gt; a search on web and the MS and MSDN didn&#39;t find me much useful about &lt;br&gt; what it actually does that&#39;s any different than any other compiler--I &lt;br&gt; couldn&#39;t even find a /trace switch in the commandline for the compiler.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/55c913b7a47d3f17?show_docid=55c913b7a47d3f17</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Fri, 27 Jan 2012 16:15:01 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/445e41befc22d41b?show_docid=445e41befc22d41b</link>
  <description>
  Let&#39;s say there&#39;s never a lack of stuff to do... :) &lt;br&gt; &lt;p&gt;--
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/445e41befc22d41b?show_docid=445e41befc22d41b</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Fri, 27 Jan 2012 15:17:36 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/13a69380285fe6b7?show_docid=13a69380285fe6b7</link>
  <description>
  Lynn McGuire: &lt;br&gt; &lt;p&gt;Lynn, &lt;br&gt; the only reason for switching you mentioned is the traceback implementation. &lt;br&gt; Care to tell us what the other reasons are? &lt;br&gt; -- &lt;br&gt; Steve
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/13a69380285fe6b7?show_docid=13a69380285fe6b7</guid>
  <author>
  esfab...@zenge.org
  (E. S. Fabian)
  </author>
  <pubDate>Thu, 26 Jan 2012 20:40:20 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/5031c89d09e0820d?show_docid=5031c89d09e0820d</link>
  <description>
  Tracebacks in the field are a given feature of &lt;br&gt; Visual C++. They are immensely helpful as I have &lt;br&gt; crashes at customers sites go to our website and &lt;br&gt; automatically tell us that the app is crashing and &lt;br&gt; where. When one has several thousand customers, &lt;br&gt; detailed crash reports are a necessity of life.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/5031c89d09e0820d?show_docid=5031c89d09e0820d</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Thu, 26 Jan 2012 18:05:28 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9c9d03a749a4191e?show_docid=9c9d03a749a4191e</link>
  <description>
  dpb wrote: &lt;br&gt; &lt;p&gt;That family farm you mentioned - enough work there to keep you busy ? &amp;lt;g&amp;gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9c9d03a749a4191e?show_docid=9c9d03a749a4191e</guid>
  <author>
  us...@example.net
  (user1)
  </author>
  <pubDate>Thu, 26 Jan 2012 17:58:39 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/94fd65a7dad72221?show_docid=94fd65a7dad72221</link>
  <description>
  That, to me at least, seems a shame to not check it out once you get the &lt;br&gt; code base cleaned up. I really can&#39;t fathom what you can gain from &lt;br&gt; having auto-generated C code over Fortran for the computational &lt;br&gt; portions...but, of course, it&#39;s not my code. &lt;br&gt; &lt;p&gt;Traceback information isn&#39;t a function of the language per se; it&#39;s a
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/94fd65a7dad72221?show_docid=94fd65a7dad72221</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Thu, 26 Jan 2012 14:59:55 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/92f370aaa16ef3c9?show_docid=92f370aaa16ef3c9</link>
  <description>
  Not even going to try. Bought a group license &lt;br&gt; of FOR_C and will be using that next. &lt;br&gt; &lt;p&gt;Moving to C++ will give us another excellent &lt;br&gt; benefit, crash tracebacks from our users with &lt;br&gt; function names and code lines. Our user &lt;br&gt; interface does this and is wonderful. The code &lt;br&gt; tracebacks that we get from OW F77 are worthless
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/92f370aaa16ef3c9?show_docid=92f370aaa16ef3c9</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Wed, 25 Jan 2012 23:36:50 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9fe54b3bdfe99350?show_docid=9fe54b3bdfe99350</link>
  <description>
  ... &lt;br&gt; &lt;p&gt;... &lt;br&gt; &lt;p&gt;That&#39;s progress, indeed... &lt;br&gt; &lt;p&gt;Will Intel compile it yet? &lt;br&gt; &lt;p&gt;--
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9fe54b3bdfe99350?show_docid=9fe54b3bdfe99350</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Wed, 25 Jan 2012 17:50:51 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/477a96b7dd02e657?show_docid=477a96b7dd02e657</link>
  <description>
  ... &lt;br&gt; &lt;p&gt;Well, the root of the problem there is badly written code to begin with &lt;br&gt; as opposed to the fundamental problem of having an insurmountable problem. &lt;br&gt; &lt;p&gt;Granted, altho one could do a search on the API names instead of the &lt;br&gt; test and ensure at least seeing all the calls. &lt;br&gt; &lt;p&gt;--
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/477a96b7dd02e657?show_docid=477a96b7dd02e657</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Wed, 25 Jan 2012 17:39:24 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/ef5c6bf35177f884?show_docid=ef5c6bf35177f884</link>
  <description>
  We are still working on getting rid of the zero &lt;br&gt; initialization of our OW F77 code. All the crashes &lt;br&gt; are gone, now we are working on computational &lt;br&gt; differences. Do not do this at home ! &amp;lt;g&amp;gt; &lt;br&gt; &lt;p&gt;Lynn
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/ef5c6bf35177f884?show_docid=ef5c6bf35177f884</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Wed, 25 Jan 2012 16:50:24 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/c30aa49cade68b09?show_docid=c30aa49cade68b09</link>
  <description>
  We are currently using OW F77s signed integers for &lt;br&gt; pointer storage and have not gotten burned yet. It &lt;br&gt; is just a little scary. We do have some old code &lt;br&gt; that is &lt;br&gt; if (iptr .gt. 0) then &lt;br&gt; do some work &lt;br&gt; end if &lt;br&gt; that has been changed to &lt;br&gt; if (iptr .ne. 0) then &lt;br&gt; &lt;p&gt;But we continually find that we have missed a couple
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/c30aa49cade68b09?show_docid=c30aa49cade68b09</guid>
  <author>
  l...@winsim.com
  (Lynn McGuire)
  </author>
  <pubDate>Wed, 25 Jan 2012 16:49:17 UT
</pubDate>
  </item>
  <item>
  <title>Re: Help on Open Watcom Dialog Editor</title>
  <link>http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9acd998e6d4c7b87?show_docid=9acd998e6d4c7b87</link>
  <description>
  ... &lt;br&gt; &lt;p&gt;... &lt;br&gt; &lt;p&gt;I should note that while unsigned integer types have not been &lt;br&gt; introduced, the F2003 Standard did define an intrinsic module for C &lt;br&gt; interoperability and a set of intrinsic functions to handle the details &lt;br&gt; in a Standard-conforming way between compatible compilers. &lt;br&gt; &lt;p&gt;While there&#39;s no absolute guarantee that two randomly chosen C and
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/openwatcom.users.fortran/browse_thread/thread/efeb9c65c54b4090/9acd998e6d4c7b87?show_docid=9acd998e6d4c7b87</guid>
  <author>
  n...@non.net
  (dpb)
  </author>
  <pubDate>Mon, 23 Jan 2012 20:55:49 UT
</pubDate>
  </item>
  </channel>
</rss>
