home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!bloom-beacon!eru.mt.luth.se!lunic!sunic!mcsun!corton!geocub!labri!goudal
- From: goudal@labri.greco-prog.fr (Frederic GOUDAL)
- Newsgroups: comp.lang.scheme
- Subject: Re: wots going on here!?
- Message-ID: <1992Sep5.075445.26848@greco-prog.fr>
- Date: 5 Sep 92 07:54:45 GMT
- References: <1187.9208311520@subnode.aiai.ed.ac.uk> <17timvINN7b8@agate.berkeley.edu>
- Sender: usenet@greco-prog.fr (le facteur fnet)
- Organization: GRECO Programmation du CNRS - Bordeaux,France
- Lines: 17
-
- In article <17timvINN7b8@agate.berkeley.edu>, bh@anarres.CS.Berkeley.EDU (Brian Harvey) writes:
- |> P.S. Yes of course if an error happens inside a procedure you should be
- |> told its name. My example was too simple, I guess. What Logo does on
- |> an error is tell you the error, the procedure in which it happened, and
- |> the line of the procedure definition that contains the error.
-
- The problem in Scheme, as I use it, is that it is not a very interesting
- information as I use a lot of continuation passing style and what I
- call "next function passing style" (as expanders in EPS) so I have a
- lot of anonymous functions, and a lot closure coming from the same
- lambda expression.
-
-
- --
-
- goudal@geocub.greco-prog.fr "Why can't we reach the sun?"
- oral-mail : babbs Pink Floyd
-