|
From: | Dr . Jürgen Sauermann |
Subject: | Re: libapl stdout |
Date: | Sat, 28 Jan 2023 12:21:06 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
Hi Jürgen (i hope you are feeling better - if you need a pint of [blood, beer, ....] these quotes are from an fpc programmer who is interested in the libapl/apl interface with fpc - i have no idea how to respond and would love something to respond with quote 1: Things would have been much easier if the library was a proper shared library.
Not sure how a GNU APL library could not be tied to APL.(and also not tied to the programming language)
so that provision for a normal call-back mechanism would have been in place.
???. My impression is that the fpc programmer has an execution model in mind thatWe/you are trying to fix something that should not have to be fixed in the first place. You can already make use of a sort of callback mechanism with APL but it still will not catch /all/ output from the library. quote 2 : Just for the record: combining output and error will not help you in communicating properly with the APL library. One channel is used for normal results, the other for indicating that there is an error and another channel that outputs additional information. And then you have your input channel. The latter can be fixed/circumvented with a call-back. Another callback also work for /one/ of the other used channels.
i have no response to either and would appreciate if you could give me an 'apl/libapl' view ... ---
[Prev in Thread] | Current Thread | [Next in Thread] |