I used it too, but abandoned it:
-it wasn't very fast, and
-it was impossible to combine it well with REXX when it had to handle dual
byte characters:
I wanted to use Pipes and Rexx to manage my vacation & family photo's, and
when I create panorama's I get names like this
GR2009_6975-GR2009_6978 - 8365x2957 - 127.16°x44.96° SCAL - Blended
Layer.jpg
When using SysFileTree, REXX gets the ° sign as 2 characters, no problem,
when REXX stores series of filenames like these in an ascii file, and when
PC-Pipes then reads that file the ° characters become something else. When
you then need REXX again to compare with fresh data from a SysFileTree, the
filenames no longer match. I was in contact with the author, and he made
quite some changes. It could work then, but still slow and unless taking
special care you could still have this (extracted from a mail in 2012):
*But, I still feel there is a large "factor of astonishment":1. you use for
example SysFileTree to get a list of files in a stem2. then you write that
list of files in a file using Pc-Pipes3. later you read that list of files
from the file back in a stemWell, the stem in step 1 and 3 are not
identical, completely unnatural in my eyes.*
I also used OS2PIPES when I had an OS/2 laptop. That author converted it
to W32PIPE to run under Windows. It is fast; I still use it for my photo
work. It was never published on the web.
If it has to handle large amounts of data, it may abend. It has a decent
subset of the VM pipelines stages, a few bugs. And, more annoying: under
Windows 10 every use of VARLOAD makes it abend. I had to use STEM, followed
by calls to REXX's VALUE function, and I'm saved once more.
I couldn't get fixes (ages ago) as the author left IBM; the source didn't
come along either. But I preciously keep it.
(the biggest photo management thing I wanted to use W32PIPE and PC-Pipes
for is now written in Visual Basic)
Kris Buelens,
--- VM/VSE consultant, Belgium ---
-----------------------------------------------------------------------
2017-02-20 4:33 GMT+01:00 DeWayne Thomas <[email protected]>:
> Actually there are two versions of this particular implementation...The
> one pointed to by the link I sent:
>
> " This is the initial release of a non .NET version of PC-Pipes. It is
> written in CPP and mirrors the .NET version in program logic and
> structure. Except for the Dispatcher and the interface between the OS
> shell evnironment and the PipeLib library, the same source code is used
> for both Windows and Linux. With typedefs and defines used to mask OS
> differences."
>
> D>
>
>
>
> On 02/19/2017 08:28 PM, Rick Troth wrote:
>
>> Thanks.
>> Yes, I had seen that one.
>> My heart sank when I saw it requires .Net.
>>
>> -- R; <><
>>
>>
>>
>> On 02/19/2017 04:08 PM, DeWayne Thomas wrote:
>>
>>> Have you looked at this one?
>>>
>>> https://sourceforge.net/projects/pc-pipelines/files/?source=navbar
>>>
>>> D>
>>>
>>>
>>> On 02/19/2017 09:40 AM, Rick Troth wrote:
>>>
>>>> How many of us crave Pipelines when working with other systems?
>>>>
>>>> I have seen at least two, probably three (maybe more) implementations of
>>>> Pipelines for systems other than CMS or MVS.
>>>>
>>>> -- R; <><
>>>>
>>>>
