[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stop
From: |
John Wiegley |
Subject: |
bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping |
Date: |
Tue, 08 Dec 2015 12:39:07 -0800 |
User-agent: |
Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.5 (darwin) |
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> I don't see any consistency issue here. But since I've already managed to
> irritate, I guess it's time for me to crawl back under my rock and let you
> decide.
Based on research by the OP, it seems that both Python and Ruby's debuggers
are idempotent in asking for results. Although, like you, I've never before
asked for the same results twice, however, we should keep consistent with
other tools, if only because there's no real reason not to.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
- bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping, (continued)
bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping, Vasilij Schneidermann, 2015/12/08
bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping, Vasilij Schneidermann, 2015/12/08
bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping, Eli Zaretskii, 2015/12/08