Let's see, what would I rather deal with.

* Another programmer's 15 function API, and a document on how to use it properly?

* Or another programmer's 15 function API, along with three macros which use the API properly, and capture all the scenarios I need based on a couple of examples.

How's this any different than taking a big ugly api and writing three shims around it to call it in the way you want?

The difference isn't whether or not code is written; the question is who/what writes it:

- Does the machine write it, using a reliable syntax rule loaded into the compiler (implemented as a macro); or

- Does the programmer, by hand (or with textual preprocessing, copy and paste, IDE help, ...).

Macros can be as smart as you want them to be.

generally, even bad api is easier to understand or debug than macro. and not all macros are well written.

Macros being hard to debug may be true of some macro systems that you know.

Not all macros are well written is a poor argument; not all anything is well written ... so don't use anything!