Newsgroups: comp.unix.questions Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!csn!boulder!news From: cdash@watneys.colorado.edu (Charles Shub) Subject: Re: Unix Stack Frame Questions Message-ID: <1991Apr5.223123.8905@colorado.edu> Sender: news@colorado.edu (The Daily Planet) Nntp-Posting-Host: watneys.colorado.edu Organization: University of Colorado at Colorado Springs References: <3465@unisoft.UUCP> <9272@sail.LABS.TEK.COM> Distribution: na Date: Fri, 5 Apr 1991 22:31:23 GMT In article <9272@sail.LABS.TEK.COM> terryl@sail.LABS.TEK.COM writes: => In article <3465@unisoft.UUCP> greywolf@unisoft.UUCP (The Grey Wolf) writes: => >/* by goehring@gnu.ai.mit.edu => > * In article <125@epic.epic.com> tan@epic.epic.com (Andy Tan) writes: => > * [ horrendously edited to address only relevant stuff ] => Repeat after me: ALL THE WORLD IS NOT A VAX!!!! Repeat that 10 TIMES. => You have to learn to think globally, instead of just your tiny => little world.... Ah... a case of model versus implementation. For Most algol like languages the invocation of procedures/functions is nested, so a model of the invocation sequence history is a stack of contexts. If a machine has hardware that looks like a stack, the mapping from the concept to the hardware is simple and natural. Otherwise, the mapping is not so simple and natural. Irrespective of the implementation, the underlying model is still a stack. -- charlie shub cdash@cs.Colorado.EDU -or- ..!ucar!boulder!cdash or even (719) 593-3492 -or- cdash@colospgs (BITNET)