Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Commit patches and wait for INRIA to merge takes a long time and my work was always delayed. So I made a branch of camlp4.But everytime I made a little change, I need to make the whole compiler, it takes a long time. What’s your best practice? (sorry If I made a stupid mistake)
(I think branching camlp4 is relatively safe, at least, you are assured binary compatible)
I don’t understand why you need to “make the whole compiler”; you should be able to recompile just the part that changed, that is Camlp4.
make camlp4out(orcamlp4opt) should be enough.You have suggested on the OCaml bug tracker to separate Camlp4 from the OCaml distribution. If you maintain a fork anyway, why don’t you try doing this on your side? I mean you could maintain a patch of OCaml that removes Camlp4 (… but still work, that is probably not so easy as it seems, but if you’re ready to hack Camlp4 you’re hard-necked anyway), and a separate distribution of Camlp4; that would solve your problem — you’d still have to merge the OCaml trunk development in your ocaml-without-camlp4 fork.
Finally, have you considered discussing this with Jérémie Dimino? He’s the current maintainer of Camlp4 (working on his free time, like other OCaml contributors), and he would probably be a good person to contact on those issues.