that might be one way to develop.

alternatively you could limit the list to all four types of "starter" methods:

1 Execute on server
2 New process
3 CALL WORKER
4 method called via menu item with "new process" enabled

there is really no need to examine every single subroutine.

that said, moving forward,
I suppose it would be good practice to make sure new project methods are marked 
as preemptive-only.

then, if compilation fails (you call a UI or printing command, for example)
you can decide whether to delegate the task to a cooperative process (CALL 
FORM),
use Signal, or uncheck the preemptive checkbox.

2019/04/12 7:37、Wayne Stewart via 4D_Tech 
<4d_tech@lists.4d.com<mailto:4d_tech@lists.4d.com>>のメール:
You should be able to work through the list (slowly).


**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to