4 ms·
Look, this can be hard to grasp. In zproject we write models of our library APIs. From these we get stuff as exotic as bindings in Java, python, Ruby, node, and
by PieterH 10y ago
Look, this can be hard to grasp. In zproject we write models of our library APIs. From these we get stuff as exotic as bindings in Java, python, Ruby, node, and all scripts to build them.
- marmaduke 10y agoHow does the system automatically manage differences between various languages when binding?
- shadowmint 10y agoThats really the key question here. As I understand it, you do it by hand.
- PieterH 10y agoYou write your own backends. These can be trivial to very comolex. See zproto or zproject for examples.
- zo1 10y agoThink of it as as generic templating library/system. It has no knowledge of the output, or the differences. The benefit is that you write one "unified" say model, or some sort of input. And then write the translation to different languages (if you want, it can just be one), and have it generate for you automatically based on the rules you coded into the translation logic.