T
Tim Kuehn
Guest
I've avoided BIND until a customer mandated it's use. The main issue I had with it is was the difference in how it behaved vs other TT models - particularly when it came to passing a BUFFER or doing a DEFINE BUFFER in a procedure / at the procedure level. These constructs would work in non-bind scenarios, I'd like to see them work in a BIND scenario. (I'd note that the version I'm using may not have the latest updates which might've fixed some of these issues.) What I'd really like to see from BIND is the ability to share a TT instance across multiple objects / procedures, and give each instance their own default buffer. Calling one routine and having it's actions change the buffer pointer in another routine is a problem I'd like to see gone. 
I'd also like to see consistent syntactical treatment between BIND, BY-REFERENCE, and straight TT.
Continue reading...
I'd also like to see consistent syntactical treatment between BIND, BY-REFERENCE, and straight TT.Continue reading...