'_DPROTO' stands for decorated prototype and this will expand prototypes for fastcall or callee declaration appropriate for the current compiler. _link_.m4 defines the m4 macros '_DPROTO', '_OPROTO' and '_VPROTO'. In the actual file there is a call to an m4 macro at the top. _DPROTO(`iyh,iyl',`iyh,iyl',void,apu_opp,uint8_t command,int8_t bank,void * operand) _DPROTO(`d,e,iyh,iyl',`iyh,iyl',void,apu_cmd,uint8_t command) The reason to do it this way is that all of the z88dk platforms can be supported, with the correct header files begin generated by the z88dk-lib tool when the library is installed. I’ve passed some example C header prototypes here to talk them through. Have a look at some of the files in this photo directory, to get the idea.

The C header file is generated for each case by the M4 tool, for all of the libraries using the example format provided. The lib files (compiled with the relevant extensions by either SCCZ80 or ZSDCC) are placed in their respective directories. The structure of the 3rd party library is defined (by example) by the way mine is done. SCCZ80 passes a minimum of 16 bit parameters, whereas ZSDCC does 8 bits where the parameter is uint8_t or int8_t equivalent. Often, this degenerates into one wrapper, particularly where 8 bit function parameters are avoided. Usually for z88dk the author writes wrappers for at least the sccz80 compiler and the two versions of the zsdcc libraries. Yes the calling conventions are not changed by how the wrappers are written. Is it the same calling convention? Meaning my wrapper should work with just a little added configuration?

Z88dk cplot black red