libera/#commonlisp - IRC Chatlog
Search
10:58:16
pve
btw, my current method of attaching instances to packages in a non-intrusive way is to intern a "special" symbol and stuff the instance in that symbol's plist :)
10:59:04
pve
storing the association in a hash table would be better, but then if the package is deleted, the hash table would have to scanned for deleted packages
11:00:06
phoe
if you control the creation and deletion of your packages then you can write your own code for your DELETE-PACKAGE
11:05:32
pve
a lot of this could be accomplished by a project specific create-package macro, so I'm not sure if all this CLOSsing around is worth it
12:08:56
pjb
gendl__: you may also consider https://gitlab.com/com-informatimago/com-informatimago/-/tree/master/common-lisp/telnet
14:23:28
pjb
Ap0gee: so you could 1- test them sequentially in any order (a first sanity check). and
14:24:11
pjb
Ap0gee: 2- test them in parallel, still independently, in separate threads. To run the tests, you'll need a thread-safe test framework, and not forget to thread-join the threads at the end, before reporting the results.
14:26:09
pjb
Ap0gee: now, of course, the parallel processes may sometimes need to have synchronisation between them. (eg. a consummer and a producer). In that case, you may try to test different situations by adding delays, or other modifications to the code, but it would be more testing the synchronization primitives than anything else. Better modelize the processes and prove they should work, using eg. CSP.
14:26:50
pjb
Ap0gee: of course, you still need to be aware of the limitations of such a formal proof. Have a look at