> On 2020-09-16, at 8:21 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> Hi Christoph,
> 
> On Wed, Sep 16, 2020 at 7:41 AM Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> Alright, then it seems fine!
> 
> 
> 
> PS: Did you know #isThisEverCalled? That's a bit cooler than "putting a halt somewhere". ;-)
> 
> 
> What would be cooler than the current implementation is something that maintains a pair of dates in the properties of a method that sends isThisEverCalled. If the method's properties are empty then isThisEverCalled would (silently) update the properties with the "start date".  Subsequent calls would set the "end date" to the current time.  We could then browse for senders of isThisEverCalled and see when exectly was the method called.  No propertiers => it wasn't called.  properties with an end date long in the past => not for a while.  The problem with an implementation based on halt is that one can only use it for code that can safely be halted.

Ooh, sneaky. Could also hook to a logger that writes to non-image output (file/stdio/mqtt/etc) to get live updates.


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Liability: a valuable political skill