thesanman112 wrote:my example I posted shows that the array has been passed to the library...
Oh sorry! Maybe I see what is going on. Passing an argument is a thing, but having it returned as one would return a packet to someone by mail, it's something else. The syntax function F(argument_passed) as returned_type , is for me of the second sort. For a library I would expect some data packet returned after you discarded the library for instance, or anything like that, like when you end a program by the instruction "END 100" so that 100 is returned.
So we were just not talking about exactly the same thing. But you are right, a function embedded in a library is still able to take an array as argument, and it's byref, and so on, just as usual. But the return value is still not an array. At least we will have to dig out a little more.
Thanks anyway for clarifying this point.
thesanman112 wrote:
I know it can be difficult to follow other peoples style of coding, I didn't use TYPE, END TYPE of any kind
or pointers to keep it simple.
I use often user defined types, but sincerely not because they are easy so much to design. I use them because the maintenance in the long term is very reduced. So I would agree with you if you meant that UDTs are not really a simplification, above all when we come to small programs that could be written in a far simpler way.