>>>>And you've to remember if there was an array named someudf[], a stored prog named someudf() ...
>>>>Cetin
>
>
>>"You still have that problem with procedure libraries." - How?
>
>Hi Cetin
>
>I mean that even with procedure libraries, you still have to worry about conflicting UDF, array and stored procedure names. In fact, I'd argue it would be worse with procedure files. You could then have a conflict in the name of two different UDFs in two different procedure libraries.
>
>
>>"The question is what is the BENEFIT of the procedure library?" - If you can make me understand the first one than nothing.
>
>The only benefit it has is that it allowed longer function names, but that's not a problem anymore because the OS let's long file names.
>
>>Probably you missed I was talking about class library files as prg not procedure files.
>
>That's probable!

"In fact, I'd argue it would be worse with procedure files. You could then have a conflict in the name of two different UDFs in two different procedure libraries."

You're absolutely mixing class library prgs with procedure files. That name conflict is intentional. Most OOP textbooks show it with a basic shape class:

Circle.Draw(...)
Rectangle.Draw(...)
Polygon.Draw(...)

If you say its purpose is not only in naming then consider another one:

XAlgorithmClass.CalculateSomething(...)
YAlgorithmClass.CalculateSomething(...)

Cetin