I like this idea. That way, the top-level "#include <bitcoin>"
directory is pure library-level headers, with all the sub-headers in
their own directories. The names "core" and "system" are both fine,
but "base" or "types" could also work.

The name "types" is nice, because it makes it clear that this library
is designed to provide the basic data types that bitcoin is built
from. The actual functionality goes in the other libraries, like
blockchain or network.

-William


On Wed, Sep 24, 2014 at 10:56 AM, Amir Taaki <genjix@???> wrote:
> hey,
>
> so we're reorganising libbitcoin into submodules like blockchain,
> server, node, ...
>
> there's a 'bitcoin' submodule which is the current main code in libbitcoin.
>
> Would it make sense to rename this to core? or system?
> So instead of:
>
> #include <bitcoin/bitcoin.hpp>
>
> We have either of:
>
> #include <bitcoin/core.hpp>
> #include <bitcoin/system.hpp>
>
> I kinda like system for what it implies.
>
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>