home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:10551 comp.lang.misc:3554
- Newsgroups: comp.arch,comp.lang.misc
- Path: sparky!uunet!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!sun-barr!decwrl!pa.dec.com!rdg.dec.com!jch
- From: jch@rdg.dec.com (John Haxby)
- Subject: Re: CLU break and continue (Was: Re: A challenge to the anti-goto)
- Message-ID: <1992Nov9.175737.28697@rdg.dec.com>
- Sender: news@rdg.dec.com (Mr News)
- Organization: Digital Equipment Corporation
- References: <1cvoctINNmhs@agate.berkeley.edu> <PSM.92Nov3165530@soma.sics.se> <BRADLEY.92Nov9101822@marley.think.com>
- Date: Mon, 9 Nov 1992 17:57:37 GMT
- Lines: 27
-
- In article <BRADLEY.92Nov9101822@marley.think.com>, bradley@marley.think.com (Bradley Kuszmaul) writes:
- |> In article <1992Nov9.114323.22688@rdg.dec.com> jch@rdg.dec.com (John Haxby) writes:
- |>
- |> ...
- |> Apart from the local/procedure-call difference the two mechanisms are
- |> identical, although `signal' tends to be expensive and `exit' is simply
- |> an unconditional branch. ...
- |>
- |> The signal is not as expensive as you might think. This is because the
-
- I should've said `relative to return or relative to exit'.
-
- Once, long ago I implemented something that treated `signal' as
- though it were a form of `return'. It wasn't fast -- the program spent
- most of its time in the signal dispatcher since (a) the offending procedure
- was used for each input token and (b) the program didn't do very much
- else. Mind you, if I'd done the same thing in Ada it may well have been
- running to this day.... (if it worked, the unhandled exception thing in Ada,
- as you say, is rather silly).
-
- --
- John Haxby, Definitively Wrong.
- Digital <jch@rdg.dec.com>
- Reading, England <...!uknet!wessex!jch>
-
- ----------------------------------------------------------------
- The opinions expressed herein are my own, not my employers.
-