Dainius (GreatEmerald): > Well, the situation is like this: D creates a list of names of files > that should be loaded by C. C then takes the list, uses it to load the > files, then stores both the pointers to the loaded files and the names > of the files in an array of structs. Then when C wants to access the > files, it asks D about which file to access, which then sends the file > name, and C compares the known file names and on finding a match, > accesses the file. > So that means that the array should be pretty much read-only there, > but C needs to know how big the newly created array of structs has to > be. As for how long the list of file names will be - it's determined > by the configuration, so it will be anywhere from 1 to around 300 or > even more.
So? Bye, bearophile