# Clang vs CBindingGen

**URL:** <https://discourse.julialang.org/t/clang-vs-cbindinggen/56693>\
**Category:** General Usage\
**Tags:** c, clang\
**Created:** [March 7, 2021, 7:06pm UTC](https://discourse.julialang.org/t/clang-vs-cbindinggen/56693 "2021-03-07T19:06:48Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Gnimuc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gnimuc/32/2194_2.png) [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)\
**Post date:** [March 15, 2021, 1:39pm UTC](https://discourse.julialang.org/t/clang-vs-cbindinggen/56693/10 "2021-03-15T13:39:34Z")

</div>

You may also be interested in @krrutkow’s new work: [GitHub - analytech-solutions/C.jl: Automatic C interfacing for Julia](https://github.com/analytech-solutions/C.jl).

The new string macro just allows users to write exactly C code, which, I think, is way better than CBinding.jl’s Julia-C-hybridized macros.

As I mentioned above, the goal of Clang.jl’s generator is to generate code that a user will write based upon Julia’s C interop docs. The goal of CBinding.jl/C.jl is to get a better user experience when working with the C interface.

---

_[View the full topic](https://discourse.julialang.org/t/clang-vs-cbindinggen/56693)._