Project

General

Profile

Feature #1388

GlobalManager: create SignalWatcher internally?

Added by John Abbott over 4 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Safety
Target version:
CoCoALib-0.99880
Start date:
09 Jan 2020
Due date:
% Done:

0%

Estimated time:
Spent time:
0.25 h

Description

Should the GlobalManager have the ability to create a SignalWatcher?
If so, should the default be to create a SignalWatcher or not to create one?

Related issues

Related to CoCoALib - Design #982: Catching interrupts in example progs?Closed2016-11-25

Related to CoCoA-5 - Bug #1385: valgrind: reports 456byte leakClosed2020-01-07

History

#1 Updated by John Abbott over 4 years ago

  • Related to Design #982: Catching interrupts in example progs? added

#2 Updated by John Abbott over 4 years ago

Is there any disadvantage to creating a SignalWatcher always?
I think it incurs essentially no run-time cost.

After reading #982, it seems that the recommended use of a SignalWatcher is to create it right after creating the GlobalManager; so perhaps the GM itself could create the SW?

Someone who wants an uninterruptible program would not want a SignalWatcher to be created; this seems like an "unusual" case to me.

#3 Updated by John Abbott over 4 years ago

  • Related to Bug #1385: valgrind: reports 456byte leak added

#4 Updated by John Abbott over 3 years ago

  • Target version changed from CoCoALib-0.99800 to CoCoALib-0.99850

#5 Updated by John Abbott about 2 months ago

  • Target version changed from CoCoALib-0.99850 to CoCoALib-0.99880

Also available in: Atom PDF