diff options
Diffstat (limited to '')
4 files changed, 93 insertions, 21 deletions
diff --git a/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md b/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md index 8d13534..f81a3fb 100644 --- a/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md +++ b/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md @@ -199,16 +199,20 @@ adapt it to emit the metadata. The alternative that rust-ffi implements relies on internals of the Rust compiler, which isn't actually worst, just less common and less accepted. -I've started a fork of cbindgen: [x-bindgen][x-bindgen-repo]. Right now it is +I've started a fork of cbindgen: ~~x-bindgen~~[^x-bindgen]. Right now it is just a copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code from it, and add a IR emitting code instead. +[^x-bindgen]: *EDIT*: now archived, the experimentation was fun. I've started to move more towards C, so this effort became deprecated. + When starting working on x-bindgen, I realized I didn't know what to look for in a header file, as I haven't written any C code in many years. So as I was writing [libedn][libedn-repo], I didn't know how to build a good C API to expose. So I tried porting the code to C, and right now I'm working on building a *good* C API for a JSON parser using parser combinators: -~~ParsecC~~ *EDIT*: now archived, the experimentation was fun. +~~ParsecC~~ [^parsecc]. + +[^parsecc]: *EDIT*: now also archived. After "finishing" ParsecC I'll have a good notion of what a good C API is, and I'll have a better direction towards how to expose code from libedn to other @@ -220,7 +224,6 @@ and property-based testing for libedn. [cbindgen-crate]: https://github.com/eqrion/cbindgen [syn-crate]: https://github.com/dtolnay/syn [rust-ffi]: https://blog.eqrion.net/future-directions-for-cbindgen/ -[x-bindgen-repo]: https://git.euandreh.xyz/x-bindgen/ [libedn-repo]: https://git.euandreh.xyz/libedn/ ## Conclusion diff --git a/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po index 262cf16..7e1e473 100644 --- a/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po +++ b/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po @@ -325,11 +325,18 @@ msgid "" " [1 :parent 0 1 true]]\n" msgstr "" +msgid "updated_at: 2021-02-09" +msgstr "" + +msgid "" +"I've started a fork of cbindgen: ~~x-bindgen~~[^x-bindgen]. Right now it is " +"just a copy of cbindgen verbatim, and I plan to remove all C and C++ " +"emitting code from it, and add a IR emitting code instead." +msgstr "" + msgid "" -"I've started a fork of cbindgen: " -"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " -"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " -"from it, and add a IR emitting code instead." +"[^x-bindgen]: *EDIT*: now archived, the experimentation was fun. I've " +"started to move more towards C, so this effort became deprecated." msgstr "" msgid "" @@ -338,12 +345,28 @@ msgid "" " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " "to build a good C API to expose. So I tried porting the code to C, and right" " now I'm working on building a *good* C API for a JSON parser using parser " -"combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +"combinators: ~~ParsecC~~ [^parsecc]." msgstr "" -msgid "updated_at: 2021-02-09" +msgid "[^parsecc]: *EDIT*: now also archived." msgstr "" +#~ msgid "" +#~ "I've started a fork of cbindgen: " +#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " +#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " +#~ "from it, and add a IR emitting code instead." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +#~ msgstr "" + #~ msgid "updated_at: 2020-11-14" #~ msgstr "" diff --git a/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po index 262cf16..7e1e473 100644 --- a/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po +++ b/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po @@ -325,11 +325,18 @@ msgid "" " [1 :parent 0 1 true]]\n" msgstr "" +msgid "updated_at: 2021-02-09" +msgstr "" + +msgid "" +"I've started a fork of cbindgen: ~~x-bindgen~~[^x-bindgen]. Right now it is " +"just a copy of cbindgen verbatim, and I plan to remove all C and C++ " +"emitting code from it, and add a IR emitting code instead." +msgstr "" + msgid "" -"I've started a fork of cbindgen: " -"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " -"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " -"from it, and add a IR emitting code instead." +"[^x-bindgen]: *EDIT*: now archived, the experimentation was fun. I've " +"started to move more towards C, so this effort became deprecated." msgstr "" msgid "" @@ -338,12 +345,28 @@ msgid "" " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " "to build a good C API to expose. So I tried porting the code to C, and right" " now I'm working on building a *good* C API for a JSON parser using parser " -"combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +"combinators: ~~ParsecC~~ [^parsecc]." msgstr "" -msgid "updated_at: 2021-02-09" +msgid "[^parsecc]: *EDIT*: now also archived." msgstr "" +#~ msgid "" +#~ "I've started a fork of cbindgen: " +#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " +#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " +#~ "from it, and add a IR emitting code instead." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +#~ msgstr "" + #~ msgid "updated_at: 2020-11-14" #~ msgstr "" diff --git a/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po index 262cf16..7e1e473 100644 --- a/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po +++ b/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po @@ -325,11 +325,18 @@ msgid "" " [1 :parent 0 1 true]]\n" msgstr "" +msgid "updated_at: 2021-02-09" +msgstr "" + +msgid "" +"I've started a fork of cbindgen: ~~x-bindgen~~[^x-bindgen]. Right now it is " +"just a copy of cbindgen verbatim, and I plan to remove all C and C++ " +"emitting code from it, and add a IR emitting code instead." +msgstr "" + msgid "" -"I've started a fork of cbindgen: " -"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " -"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " -"from it, and add a IR emitting code instead." +"[^x-bindgen]: *EDIT*: now archived, the experimentation was fun. I've " +"started to move more towards C, so this effort became deprecated." msgstr "" msgid "" @@ -338,12 +345,28 @@ msgid "" " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " "to build a good C API to expose. So I tried porting the code to C, and right" " now I'm working on building a *good* C API for a JSON parser using parser " -"combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +"combinators: ~~ParsecC~~ [^parsecc]." msgstr "" -msgid "updated_at: 2021-02-09" +msgid "[^parsecc]: *EDIT*: now also archived." msgstr "" +#~ msgid "" +#~ "I've started a fork of cbindgen: " +#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a " +#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " +#~ "from it, and add a IR emitting code instead." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +#~ msgstr "" + #~ msgid "updated_at: 2020-11-14" #~ msgstr "" |