(j3.2006) C1x standard
Keith Bierman
khbkhb
Thu Dec 22 16:29:17 EST 2011
The compiler writer(s) may support a bevy of platforms. They may even have to cope with multiple C compilers on several of the platforms
I agree that it would be a great kindness to users if there was less underlying complexity and layers
But the current industry trend is to encapsulate an entire stack in a VM rather than "just" solve minor issues between C programs (or C C++ perl and java version skew)
Sent from my iPad
On Dec 22, 2011, at 2:11 PM, Van Snyder <Van.Snyder at jpl.nasa.gov> wrote:
>
> On Thu, 2011-12-22 at 08:45 -0800, Keith Bierman wrote:
>> I would much rather this be the responsibility of the
>> processor, since it's much more likely that a processor and
>> operating system will be in sync in some distant future galaxy
>>
>>
>> I won't try to insert myself into the technical discussion proper. But
>> trying to foresee too far into the future (psychohistory anyone?) is
>> fraught with peril. That processors and OS's come from the same (or
>> even cooperating) organization(s) has sometimes been true, sometimes
>> not. C and Fortran compilers might well have no connection other than
>> whatever is specified in one (or both) Standards of a particular
>> vintage.
>>
>>
>> The IBM zSeries (originally S360, and with appropriate dated emulators
>> even older binaries can still be run) does illustrate how well
>> backward compatibility can be maintained over long timeframes. But
>> that appears to be more the exception than the rule.
>
> Even so, there's one organization responsible for the Fortran compiler,
> and far more users of it. It would be a kindness to the dozens
> (thousands?) of users of a compiler if it were to solve this problem,
> instead of foisting it onto all the users.
>
>> Keith Bierman
>> khbkhb at gmail.com
>> kbiermank AIM
>> 303 997 2749
>>
>>
>>
>>
>
> _______________________________________________
> J3 mailing list
> J3 at j3-fortran.org
> http://j3-fortran.org/mailman/listinfo/j3
More information about the J3
mailing list