🚀 go-pugleaf

I'm interested in learing what the C idioms are for "extern" functions.

The reason I ask is because external functions have global scope, and some
convention has to be established to avoid name clashes.

Here is a fragment of a (bounded) stack I wrote:

#ifndef BOUNDEDINTSTACK_H
#define BOUNDEDINTSTACK_H

typedef struct BoundedIntStackRep* BoundedIntStack;

void newBoundedIntStack (int maxDepth);

int topBoundedIntStack (BoundedIntStack stack);

void popBoundedIntStack (BoundedIntStack stack);

void pushBoundedIntStack (BoundedIntStack stack, int item);

...

#endif BOUNDEDINTSTACK_H

I'm interested in knowing what coding conventions a seasoned
C programmer would have used to code this abstract data type.

For example, do you qualify the subprograms before or after the
"real" name:

int topBoundedIntStack (BoundedIntStack stack);

   vs.

int BoundedIntStackTop (BoundedIntStack stack);

Would you have coded a different stack module for each kind of
native type?  Or just use a BoundedLongStack for all integer types
(letting the compiler automatically coerce the item into type long)?

Steve Summit gave a recommendation in his book on how to
code an abstract data type.  Steve: is the example I provided what
you had in mind?

matt