OK, I've updated gpc and begun to probe for "clarification."
I'm glad an automated c-header translator is being discussed. The fpc people have such a tool and have translated libc. A terrific pascal development.
One issue to consider is naming conflicts. Since dot qualified names seem to be a problem, perhaps prepending the c library name to the pascal name will avoid name conflicts.
For example using the fpc unit "libc"; the libc function "close()" takes a file descriptor parameter, while the native pascal "close()" takes a file type parameter. Thus, the fpc libc "close()" is singled out and renamed in "unistdh.inc" to "__close()". (if memory serves me) Perhaps such a naming confusion can be avoided with all libc imports being named libc_name().
A libc unit for pascal is a big departure from the dos world. Other c-libs like OpenGL, etc. will follow.
I really don't care about ISO-this or ISO-that. Pascal is an elegant language that should allow casual programmers to tap into the c-library platform without too many paw prints.