>I mean that if you have procedures/functions there is no value in having them in a library to foxpro at runtime. The library is possibly convenient for sharing the content with other developers - by copying a single file to that developer. In a team environment, libraries just block multiple developers building functions/procedures in the same library - requiring source control to integrate - not a perfect solution. Similarly many classes in a single vcx is a problem for teams. It's worse than the procedure library because the vcx is a binary file. At runtime though, a vcx must be opened with set classlib unless you use newobject. So there is a benefit to multiple classes in a single library at runtime, but not a design time.

My POV is that is a pain to do classes in prg's. I have done development in a multi developer environment for a decade or so and we never had problems with mulitclass libraries. Same to prg's, header files or included tables. It's just a question of organisation - clear responsibility. MS VSS is mandatory, yes, but this would not change with a single class per wathever solution. It has more benefits. One might use tools, but VSS integrates number one fine in the IDE.
What is SET CLASSLIB? In an exe the vcx's are in focus anyway and I use NEWOBJECT via a table based class factory.
For functions and procedures, they are that rare in this system, so I simply don't care. They are mostly used for SQL SELECTS. Again, since they are part of the exe no SET PROCEDURE etc is needed.

But this pure academic. I will not change this horse. It's old and it is a good race.