home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!firth
- From: firth@sei.cmu.edu (Robert Firth)
- Subject: Re: What's wrong with stack machines?
- Message-ID: <1992Nov5.144403.6359@sei.cmu.edu>
- Organization: Software Engineering Institute
- References: <17035@mindlink.bc.ca>
- Date: Thu, 5 Nov 1992 14:44:03 GMT
- Lines: 16
-
- In article <17035@mindlink.bc.ca> Nick_Janow@mindlink.bc.ca (Nick Janow) writes:
-
- >You have to consider stack machines according to their own strengths, not how
- >well or not well they handle non-stack language programming techniques.
-
- Maybe I'm misinterpreting, but what this sounds like to me is "Don't
- evaluate stack machines by how well they perform running real code in
- existing languages. Look at how well they execute unreal code in
- nonexistent languages."
-
- After all, if a stack machine performs badly on almost all existing code,
- and almost all future code written in existing languages, isn't that a
- very strong argument against building one? If you disagree, then I have
- this automobile to sell you. It's got half the fuel consumption of a
- conventional automobile, provided you only drive it on specially built
- roads.
-