> Forth is another good example. There’s no call and return Huh? Could have fooled...well, everyone, including Chuck Moore. Emphasis mine. https://web.archi

> Forth is another good example. There’s no call and return Huh? Could have fooled...well, everyone, including Chuck Moore. Emphasis mine. https://web.archive.org/web/20060101073958/http://www.colorforth.com/cf.html https://web.archive.org/web/20060101073958/http://www.colorf... "The Data stack holds parameters for and results of subroutine calls. This distinction between control and data minimizes the cost of subroutine calls. https://en.wikipedia.org/wiki/Forth_(programming_language) https://en.wikipedia.org/wiki/Forth_(programming_language) "Forth is a procedural, stack-oriented programming language..." "...where the user interacts via subroutines called words. " "First a number (1 or 8) is pushed onto the stack, FLOOR5 is called,..." "This is the same as what a processor's call/return instructions do." https://www.forth.com/resources/forth-programming-language/ https://www.forth.com/resources/forth-programming-language/ "The benefit of having a stack reserved for return addresses was that the other stack could be used freely for parameter passing, without having to be “balanced” before and after calls" ...