guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about your profiling patch...


From: Keisuke Nishida
Subject: Re: Question about your profiling patch...
Date: Wed, 04 Apr 2001 21:25:33 -0400
User-agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/21.0.99 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

At 04 Apr 2001 19:47:01 -0500,
Rob Browning wrote:
> 
> > Hmm, this is mysterious.  It's not at a tail position, and I don't
> > understand why putting a print statement changes the behavior.
> > I don't have any idea of how to fix it right now, sorry.
> 
> If it helps, I wasn't claiming that putting in the print statement
> changed the behavior -- I presume the profiler would still list its
> number of calls at 0.  I just meant that by putting in the print
> statement, I could see that it was in fact being called, even though
> the profiler was saying that it wasn't.

I see.  But I still don't know what is wrong with this.
Could you try with simpler examples?  What happens with
the followings, for example:

(define (foo)
  (let ((x #f))
    (begin (set! x (bar))
           (or x x))))

(define (foo)
  (let ((x #f))
    (begin (bar)
           (or x x))))

(define (foo)
  (let ((x #f))
    (set! x (bar))))



reply via email to

[Prev in Thread] Current Thread [Next in Thread]