M
marian.edu
Guest
It just might you’ve been reading too much OERA already and it’s probably best to enjoy more pleasant literature once in a while 
There is hardly anything ‘decent’ abut such a beast and clearly your class it trying to do too much work on its own. You’re most probably trying to produce some form of output for data integration and the first obvious option seems to be to load everything in a dataset and then serialise that so that the other party understand it. This might work just fine if the data there is somehow limited, else another option is to use a ‘writer’ or an output stream and then just send various information into that one instead of preparing everything upfront and serialise afterward. For passing 20 parameters to a routine you better go with a ‘parameter object’ (Stefan mentioned that once, he will probably tell you more about it) and in 4GL world a temp-table or even a dataset are the easiest way to create those kind of ‘state only’ objects that can be used to pass information around. As long as you don’t pass that by reference it won’t affect the encapsulation and hence not ruin your karma, mind you in OO world encapsulation is not exactly that strict… it’s perfectly valid at times to have a list and give access to that to the outside world so anyone can update that directly instead of writing wrapper methods to get/add/delete objects in that list. Bref, if you still want to load everything upfront then just make an object that will hold that data and pass that around to all routines that need to fill data into it… do let anyone update the object, it’s not holding any logic anyway so just make it as lightweight as possible. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
There is hardly anything ‘decent’ abut such a beast and clearly your class it trying to do too much work on its own. You’re most probably trying to produce some form of output for data integration and the first obvious option seems to be to load everything in a dataset and then serialise that so that the other party understand it. This might work just fine if the data there is somehow limited, else another option is to use a ‘writer’ or an output stream and then just send various information into that one instead of preparing everything upfront and serialise afterward. For passing 20 parameters to a routine you better go with a ‘parameter object’ (Stefan mentioned that once, he will probably tell you more about it) and in 4GL world a temp-table or even a dataset are the easiest way to create those kind of ‘state only’ objects that can be used to pass information around. As long as you don’t pass that by reference it won’t affect the encapsulation and hence not ruin your karma, mind you in OO world encapsulation is not exactly that strict… it’s perfectly valid at times to have a list and give access to that to the outside world so anyone can update that directly instead of writing wrapper methods to get/add/delete objects in that list. Bref, if you still want to load everything upfront then just make an object that will hold that data and pass that around to all routines that need to fill data into it… do let anyone update the object, it’s not holding any logic anyway so just make it as lightweight as possible. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...