JM->  That's true +/-. You can link functions that are in 'C' libraries,
JM-> but you _must_ extract they from the .lib to an .obj before you try
JM-> to use them. Many functions can't be full extracted because you must
JM-> extract the function, and all function that this function calls (
JM-> confused ? me too :-) ).
That makes sense, thanks for explaining it.
JM->  JG> procedure PUTSCREEN (x,y,x1,y1,array) for example?
JM->
JM->  What ? I don't known PUSCREEN function :-?
It's in one of the TC libraries, but instead of going through all this,
I found a similar command in PBVision, I believe (or PBwizard, can't
remember which...) which allows everything from .OBJ files and VGA
screens converted to .OBJ files to be inserted into an array in memory
and called for FAST screen action, fully internalized.
I'll bload other screens, but the main screen I want internalized.
JM->  You may avoid the use of 'C' functions, expecially complex functions
JM-> like 'printf', 'scanf', etc. Use 'C' functions to do hard work that
JM-> need a lot of computing speed over a block of data; like computing
JM-> CRCs, mixing data, etc. To avoid problems don't use 'C' functions and
JM-> bigger data structures that can fill your stack.
I'll increase the $stack, and do other things if I decide to try this
some more.  But your words of wisdom are what I was looking for.  Knowing
the caveats helps me decide which method I should implement.
Thanks again!
-James
--- QuickBBS 2.80 GoldBase (Zeta-1)
---------------