[wg-camlp4] getting bitstring to work with Core

Malcolm Matalka mmatalka at gmail.com
Tue May 28 17:46:14 BST 2013

I solved this for myself may by limiting the bitstring specific stuff to
their own function "let module Char = ...".
IMO the bigger issue is the error messages not making any sense than the
actual problem.

 On May 28, 2013 6:40 PM, "Stephen Weeks" <sweeks at janestreet.com> wrote:

> > It's the build system integration that fills me with dread (figuring
> > out the ocamlfind META runes, how to plumb this through to ocamlbuild,
> > OASIS and OMake, and activate it only for files that use Core).
> I see.  Waiting for namespaces might be the way to go then.
> One way that might simplify the build-system nightmare a bit would be
> to always have the Caml module in scope and to have bitstring always
> generate references to it, whether or not one is compiling against
> Core.
> --
> You received this message because you are subscribed to the Google Groups
> "ocaml-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ocaml-core+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/wg-camlp4/attachments/20130528/ce6ca342/attachment.html>

More information about the wg-camlp4 mailing list