J
jquerijero
Guest
[quote user="Jeff Ledbetter"] "What are you trying to achieve?" Performance. We want to avoid passing around possibly large datasets. "How do you use this functionality?" From a procedural/super-procedure POV: For BIND, a specific use-case is when we have a large dataset that could be used in different ways depending upon the usage context so we'll start the appropriate SUPER and BIND to the instance in the caller. Or, if there some common logic that may act upon a dataset regardless of context, that routine is started super and then BIND is used bind to the instance in the caller. This occurs in some of our MVP patterns. Another BIND use case is when we want to "borrow" the dataset in a super so we'll OUTPUT dataset BIND to a reference-only dataset in the caller. We use BY-REFERENCE when the client has sent a dataset to the server. From our service layer, that dataset is then passed along BY-REFERENCE deeper into the application to avoid deep-copy of a potentially large dataset. "What challenges do you face using the functionality?" Syntax was somewhat clunky at first and it's not always immediately obvious. "Anything else pertinent to BIND/REFERENCE passing of data structures?" Please don't change they syntax. We have it working. 
[/quote] This is pretty much how we use the features. The main headache I normally encounter is making sure that the proper keyword (BIND, BY-REFERENCE) is included in parameter definition. If you missed it, it is hard to chase.
Continue reading...
[/quote] This is pretty much how we use the features. The main headache I normally encounter is making sure that the proper keyword (BIND, BY-REFERENCE) is included in parameter definition. If you missed it, it is hard to chase.Continue reading...