On 2015/9/29 17:34, Faré wrote:
> On Tue, Sep 29, 2015 at 11:03 AM, Mark Evenson wrote:
>> I wanted to confirm with ASDF developers that as far as I can tell from
>> wrangling with UIOP:RUN-PROGRAM, it isn't going to do what I want
>> because there is no "asynchronous" mode.
> UIOP:RUN-PROGRAM i
> In a potentially memory constrained environment, I need to portably
> (across sbcl and ccl at least) process a potentially large (multiple
> GiB) stream of bytes output from a Linux command. For the curious,
> "process" here means encrypt with a block cipher and push to the
> network; whereas th
On Tue, Sep 29, 2015 at 12:14 PM, Mark Evenson wrote:
> Is their any informal ASDF policy on the stability unexported symbols
> like UIOP::%RUN-PROGRAM? I suspect y'all reserve the right to yank the
> rug at any point, right? Given that UIOP::%RUN-PROGRAM abstracts the
> Lisp implementations cap
On Tue, Sep 29, 2015 at 11:03 AM, Mark Evenson wrote:
> I wanted to confirm with ASDF developers that as far as I can tell from
> wrangling with UIOP:RUN-PROGRAM, it isn't going to do what I want
> because there is no "asynchronous" mode.
UIOP:RUN-PROGRAM itself is synchronous only, but its intern
