English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Migration to OCaml 5 requires updating a lot of C bindings due to the removalof naked pointer support. Writing OCaml user-defined primitives in C is anecessity, but is unsafe and error-prone. It does not benefit from eitherOCaml's or C's type checking, and existing C static analysers are not aware ofthe OCaml GC safety rules, and cannot infer them from existing macros alone.Thealternative is automatically generating C stubs, which requires correctlymanaging value lifetimes. Having a static analyser for OCaml to C interfaces isuseful outside the OCaml 5 porting effort too.  After some motivating examples of real bugs in C bindings a static analyseris presented that finds these known classes of bugs. The tool works on theOCaml abstract parse and typed trees, and generates a header file and a callermodel. Together with a simplified model of the OCaml runtime this is used asinput to a static analysis framework, Goblint. An analysis is developed thattracks dereferences of OCaml values, and together with the existing frameworkreports incorrect dereferences. An example is shown how to extend the analysisto cover more safety properties.  The tools and runtime models are generic and could be reused with otherstatic analysis tools.

Targeted Static Analysis for OCaml C Stubs: eliminating gremlins from the code