On Sunday March 10 1996 at 04:20, Peter Fitzsimmons wrote to Coridon Henshaw:

 PF> If you gave me some idea of your API

It's basicly a recursive file find function that populates an array with
all the files found in and under a given path.  Space for each file name is
seperatly malloc()ed and a pointer to the name is stored in the array.

The array is allocated by the caller passed to the function as a pointer.  
The function realloc()s the array if it runs out of space.

I will be modifying the function to allocate the array itself and then
adding a destroy API to free() the file names and the remainder of the
array data.

 PF> i'd probably be able to suggest a logical "close" or
"destroy" api.

Yeah, I figured that one out a few hours after I wrote the message.

I'm totally self-taught in programming (although I've been messing around
for 5 years now, mostly with BASIC) so I tend to take a little longer to
find a solution to a given problem.  And the solution that I come up with
is often unorthodox to say the least.

This thing that I've been having problems with, which you may have seen
floating around as FBDIFF, is only my 3rd non-trivial C program.

 PF> When you use C++ classes,  this type of approach is a natural part of the
 PF> language.

I've been learning C++, but I haven't done anything with it yet.  The OO
overhead doesn't seem to justify the easy of maintance just yet.

--- GoldED/2 2.50 UNREG