home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!news.byu.edu!news.mtholyoke.edu!nic.umass.edu!m2c!crackers!transfer.stratus.com!sw.stratus.com!nick
- From: nick@sw.stratus.com (Nicolas Tamburri)
- Newsgroups: comp.sys.mac.oop.misc
- Subject: Re: Q: What's your opinion?
- Message-ID: <1eivafINN8g@transfer.stratus.com>
- Date: 20 Nov 92 15:13:19 GMT
- References: <1eab2mINNild@agate.berkeley.edu> <1992Nov17.122020.6140@reed.edu> <1eattdINN9dc@transfer.stratus.com> <1992Nov20.020144.4110@selway.umt.edu>
- Organization: Stratus Computer, Inc.
- Lines: 12
- NNTP-Posting-Host: osa.sw.stratus.com
-
- In article <1992Nov20.020144.4110@selway.umt.edu>, ogd@selway.umt.edu (ozymandias G desiderata) writes:
- > What, exactly are the differences between Yerk and MOPS? The manual
- > sorta said, but it mostly seemed to be identical to the Yerk manual.
-
- The difference is mostly under the hood: Yerk compiles tokens which are then
- interpreted at runtime (indirect threading). Mops compiles subroutine calls to
- primitives (JSR threading,) and augments this by being able to compile machine
- code inline when directed to do so and JSRs for longer ones. It also does a
- good bit of optimization The result is that Mops is much faster than Yerk,
- but Yerk can make it much easier to decompile and debug most routines.
-
- /nt
-