Recently I changed the interface for invoking the compiler at runtime on generated code to use proof data slots rather than unsychronized references. The consequence is that there are a lot of non-joinable proof data slots laying around in the same module, cf. http://isabelle.in.tum.de/reports/Isabelle/rev/f6ab14e61604
Maybe it would be better to avoid proof data slots entirely in that case
any use thread-local state variables or something like that? The
crucial issue is that compiler invocation essentially is a function of
type string -> unit but somehow a result has to be returned, which must
occur through a side effect.
Florian
--
Home:
http://www.in.tum.de/~haftmann
PGP available:
http://home.informatik.tu-muenchen.de/haftmann/pgp/florian_haftmann_at_informatik_tu_muenchen_de
signature.asc
Description: OpenPGP digital signature
_______________________________________________ isabelle-dev mailing list [email protected] https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
