Paul Moore wrote: > The array module is built in, so it's > written in C - what needs to be exposed to qualify as a "C API"?
I think he's referring to the fact that there is no public array.h header file provided that lays out the C-level details. In fact, last time I looked I don't think there was any array.h file at all, it was all inside array.c. You can fake it by copying the relevant declarations into your own .h file, but then there's no assurance that you're not relying on implementation details that could change. A published interface would be much more reassuring. With the new buffer interface, probably just providing that would be sufficient, together with a C function for creating an array. The internals could still remain private if desired. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
