🚀 go-pugleaf

In article <4ft4m0INN5oh@museum.cis.ohio-state.edu>,
scruggs@news.cis.ohio-state.edu (kevin eugene scruggs) wrote:

> In article <4ft3ld$otf@nuke.csu.net> ghansen@isc.sjsu.edu (Gregory L
Hansen) writes:
> |In article <bouldin-1102962015030001@async098.nist.gov|,
> |Charles Bouldin <bouldin@enh.nist.gov| wrote:
> ||In article <9602092127.AA24456@ues5.cern.ch|, Dan Pop
> ||<danpop@ues5.cern.ch| wrote:
> ||
> ||| of the code is left untouched.  That is, unless the port is to MacOS and
> ||| the portable part has to be stuffed with WaitNextEvent calls.
> ||| 
> ||| Dan
> ||| -- 
> ||| Dan Pop
> ||| CERN, CN Division
> ||
> ||Do you *read* the posts in this thread? Or do you just keep repeating
> ||yourself regardless of what anyone else says? How can you work at CERN and
> ||be unaware that the number crunching codes that you speak of are mostly
> ||fortran. As I and several others have pointed out, 2 different fortran
> ||compilers on the Mac AUTOMATICALLY put in WaitNextEvent calls. The
> ||portable source code remains completely untouched. I've ported over
> ||100,000 lines of fortran that way, and it works fine.
> |
> |
> |I didn't know that.  But I must say, it sounds mighty conveniant.
> |
> |But, what if the number crunching code isn't in Fortran?  Mine isn't.
> |
> 
>         Demand more from software vendors.


I sent in a "feature request" to Metrowerks asking them to do what
Language Systems and Absoft already do. Perhaps if they here from more
people they will listen? They have a good track record for listening.