Re: restated question about externals



apm wrote:
| Does the standard in some direct, indirect or convoluted manner require that
| the caller of an EXTERNAL maintain the stack?

No.

The standard does not even know what stack is. It wouldn't surprise me
if there was a Fortran for stackless machines.

CVF has (had?) the default calling convention STDCALL, where the callee
cleans the stack. IVF (and possibly others) have that as an option. If the
compiled code is standard-conforming, the stack cleaning mechanism doesn't
matter.

| Fortrans I've used seem to work this way. I'd feel better if it in some way
| were required by the standard.

My condolence :-).

--
Jugoslav
___________
www.xeffort.com

Please reply to the newsgroup.
You can find my real e-mail on my home page above.
.



Relevant Pages

  • Re: Is C99 the final C? (some suggestions)
    ... > Dijkstra's weighted shortest path algorithms were nice for client-server based ... but the future is peer 2 peer. ... >>The C standard specifies what is UB and what's not. ... I can do no such thing with stack ...
    (comp.lang.c)
  • Re: Is C99 the final C? (some suggestions)
    ... > the standard? ... There doesn't have to be any mention of "stack" in what I try to ... "There are five standard signed integer types, ... standard-like language. ...
    (comp.lang.c)
  • Re: The Art and Science of Factoring
    ... Even the following is not nesting. ... It also means it has extended beyond what is required by the standard. ... In some systems that data is left on the stack, ... overwrites the data from the first definition, ...
    (comp.lang.forth)
  • Re: Toward a Forth thats easier to learn
    ... Because loops use the return stack. ... standard. ... portability. ... I'm saying that writing standard code demands new ...
    (comp.lang.forth)
  • Re: Why GCC does warn me when I using gets() function for accessing file
    ... standard does not define the term "variable". ... other people keep claiming -- that C doesn't have a stack (if function ... Where the analogy falls down, however, is that that above code can be ... but the standard *CANNOT* specify that guarantee. ...
    (comp.lang.c)