libredwg VS precautionary

I have a much better and oracti al solution: https://github.com/LibreDWG/libredwg/blob/7d9fc3da44bbdb60a4...

free is way too slow if not needed, so detect valgrind via its API. Just on valgrind to the unnecessary free dance. ASAN's memleak detector is disabled via its env.

Perl5 does its final destruction similarly, only when it has important destructors (like IO, DB handles and such) to call.

Now even for your local github action:

https://github.com/LibreDWG/libredwg/blob/master/.github/wor...

Behind the scenes we’re using the open source LibreDWG library to run a number of AutoCAD native commands such as DATAEXTRACTION.

I use it for reverse engineering unknown struct layouts for DWG classes. A field packing problem.

I'm using picat, a better Prolog dialect, and generate the facts automatically from C to generate the field layouts via picat automatically.

https://github.com/LibreDWG/libredwg/blob/master/examples/AC...

optimization problems as in compilers are extremely natural in Prolog.

after loaded https://github.com/dcnorris/precautionary/blob/main/exec/prolog/dsl.pl

One of the most interesting applications of Prolog I have seen in the recent past is the formalization of dose finding trials that occur in clinical oncology. In particular, David C. Norris has implemented a Prolog formulation of the Cumulative Cohort Design (CCD) as part of his precautionary package:

https://github.com/dcnorris/precautionary/blob/main/exec/pro...

This formulation can be used to exhaustively enumerate all possible arising cases, and also complete partially given information. It is possible to ask interesting questions about the trial as a whole, such as whether specific cases can arise. In this sense, the formulation truly serves as a declarative specification of trial designs that are otherwise stated only comparatively informally in the medical literature, and even subject to divergent interpretations.