Split up binding.cc

[vweevers]

TBD after #540 is merged.

[ralphtheninja]

I have no problem with splitting binding.cc into multiple parts. I propose something like:

$ tree src/
src/
├── batch.cc
├── batch.h
├── common.cc
├── common.h
├── database.cc
├── database.h
├── iterator.cc
├── iterator.h
├── main.cc
├── workers.cc
└── workers.h

0 directories, 11 files

@vweevers I also thought that maybe you could do this. It would be a good exercise for you to get some of that code into your head, so it's not only in mine. WDYT?

[ralphtheninja]

Or maybe:

$ tree src/
src/
├── common.cc
├── common.h
├── context.cc
├── context.h
├── main.cc
├── workers.cc
└── workers.h

0 directories, 7 files

Where context.{h,cc} would contain Database, Iterator and Batch classes.

[vweevers]

I also thought that maybe you could do this. It would be a good exercise for you to get some of that code into your head, so it's not only in mine. WDYT?

Sure! I'm open to it. No promises as to when, but that's fine, there's no rush on this.

[ralphtheninja]

Came to think of it, common.{h,cc} might not even be needed if we do context.{h,cc}.

[vweevers]

By "common" you mean the macros and helpers?

[ralphtheninja]

By "common" you mean the macros and helpers?

Yeah, basically any code that needs to be shared between files. Macros and function signatures goes into the header file, function implementations in .cc.

[vweevers]

I'm fine with the way it is now.