Actually we are using ?b2l/?l2b and some other macros to make the code
shorter and ease our development. All these macros are in the main
include file couch_db.hrl used everywhere in the code.

Since this include will be likely used in CouchDB plugins created by
users, I would like to have these kind of macros separated in their
own include file. Something common in C world. The main reason is to
not pollute namesspacing in external plugins and let them import only
what they need, ie couchdb types/records.

What do you think about it? Also, not related but maybe it could be a
good practice to enforce the use of these macros in all the couchdb
codebase like suggest filippe.

Any thoughts ?

- benoƮt

Reply via email to