Re: http or tcp/ip



<gary.l.scott@xxxxxxxx> wrote:

However, it is insufficient. We need to be able to specify things
like where stack cleanup is to occur. I don't just want to work with
a companion processor, I want to be able to produce code that works
with a processor that I may not have but that I know its argument
passing convention.

You just aren't likely to ever (well, forseeably) be able to do that in
a standard way. That's too much into non-portable implementation
details. I understand needing to be able to do such things. But that's
just not something the standard is going to be of much help in. Try to
push it if you want (not that you need my permission), but I think it
would be wasted effort. The cost/benefit of putting things like that
into the standard doesn't seem even close to there. The costs are very
large - even to specify such things in appropriate standard-speak; and
the fraction of people who it would benefit seems small. Yes, I
understand that you would be one of those people and that there are also
others, but it doesn't seem like a very large set.

--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.



Relevant Pages

  • Re: http or tcp/ip
    ... like where stack cleanup is to occur. ... a companion processor, I want to be able to produce code that works ... just not something the standard is going to be of much help in. ... would be wasted effort. ...
    (comp.lang.fortran)
  • companion processor
    ... Is there any notion of a potential "companion processor" in standard C? ... Is it maybe one of those things that was never written because everyone wanted to have it be the lingua franca. ... Or maybe some non-binding agreement? ...
    (comp.lang.c)
  • Re: http or tcp/ip
    ... a companion processor, I want to be able to produce code that works ... just not something the standard is going to be of much help in. ... would be wasted effort. ... Does windows API live in standard fortran anywhere? ...
    (comp.lang.fortran)
  • Re: how to pass a variable if type is not known?
    ... I didn't skim the standard to learn that C is the language of interop; ... elaboration being part of the reason for the book. ... "companion processor" in first bullet in chapter 15, ...
    (comp.lang.fortran)