From: <hp...@we...> - 2022-06-14 11:02:52
|
Hello Rony! Am 13.06.2022 um 13:29 schrieb Rony G. Flatscher: > ooRexx comes with a pipe.cls that defines the following stages: > > ::class pipeStage public -- base > pipeStage class > ::class SecondaryConnector subclass pipeStage > [...] Nice! It is also part of ooRexx 4.2.0 (Feb 22 2014), but recently somebody (bigrixx) added some more stages. > To see how one can use the ooRexx pipe.cls look up > "ooRexx\samples\usepipe.cls". Probably a typo: ...\usepipe.rex > If you look up pipe.cls you should > also see the programming pattern of the stages such that you might > be able to add new stages of your own. Yes -- if all else fails ;) > It may be the case that your needs can be met with the means > ooRexx has on board already. Honestly, what I "do need" (I'm hobbyist) can be done with ooRexx. My zest/request/demand for pipelines is because I am used to it. Formerly, at work, Pipelines _multiplied_ the value of the mainframe by 2..3 for me concerning my "challenge". Many tasks are solved much simpler by "pipe-thinking" it, less code is also less habitat for bugs. But -- frankly -- what is the big advantage, what makes the difference? For me it's foremost the vast number of possible sources and sinks for data flow, married with a practice-oriented set of stages that covers almost unlimited possibilities. This said (many words with just the intention not to debase any effort to copy the role model) I hope you fathom that for me "the Book" -- http://vm.marist.edu/%7Epipeline/pipeline.pdf -- is the point of reference. And assumedly you also know the warning about "those with one book only" ;) Best, M. |