[Gomp-discuss] Organization of libgomp source code

[Scott Robert Ladd]

I'm wondering about the best ways to organize the .c files for libgomp.

It seems to me that we should have a separate .c file for each function.
Naming these individual files, however, could be problematic, given the long
names of the OpenMP functions. For example, for the omp_set_num_threads
function, we could have the following names:

libgomp_set_num_threads.c
omp_set_num_threads.c <<-- my preference
set_num_threads.c

Some sort of prefix (libgomp_ or omp_) makes sense, even though we keep the
code in its own directory.

And, of course, we can use dashes instead of underscores (although the
udnerscores reflect the actual function names).

I couldn't find a filename length restriction in the GNU standards.

Attached is a libgomp.h that reflects the comments from this group. Are the
issues with the cvs worked out yet?

..Scott

libgomp.h
Description: Text document