Hello,
I am tinkering with factor and was wondering if it is OK to pick your
brains here? As I play around with the language questions come up that
are probably easy for you to answer. I don't see much action on the
#concatenative IRC channel so I thought the maling list might be a
better plac
Hi Peter,
On Mon, Nov 7, 2016 at 3:07 PM, wrote:
> Hello,
>
> I am tinkering with factor and was wondering if it is OK to pick your
> brains here? As I play around with the language questions come up that
> are probably easy for you to answer. I don't see much action on the
> #concatenative IRC
Hi Jon,
On 2016-11-07 22:34, Jon Harper wrote:
> Hi Peter,
>
> On Mon, Nov 7, 2016 at 3:07 PM, wrote:
>
>> Hello,
>>
>> I am tinkering with factor and was wondering if it is OK to pick your
>> brains here? As I play around with the language questions come up that
>> are probably easy for you t
>
> In that case I guess the mailing list makes more sense. Unless there's
> people reading the IRC logs and not part of the mailing list.
>
The mailing list can be a fine place, or GitHub issues if you run into some
problems with Factor. If you are worried about higher volume of
conversation, yo
Hi John,
On 2016-11-08 16:52, John Benediktsson wrote:
>>
>> In that case I guess the mailing list makes more sense. Unless there's
>> people reading the IRC logs and not part of the mailing list.
>>
>
> The mailing list can be a fine place, or GitHub issues if you run into
> some
> problems w
>
> I thought of parallel-map first but I wanted to do a bit more than that,
> otherwise I could just write a script that handles one and feed it to
> GNU parallel. I wanted to achieve more than what I can with GNU parallel
> (which is able to parallelize on multiple cores and writes correctly to
>
On Wed, Nov 9, 2016 at 4:02 AM, wrote:
>
> There are my last 2 attemps. The first, commented out version finishes
> without waiting for the threads to finish (even with the ugly hack of
> reading the state>> of the thread) while in the second the receiving
> thread doesn't read the messages as th
Hi Chris,
On 2016-11-08 23:58, Chris Double wrote:
> I tried to duplicate the basics of your code with the following:
>
> self '[ "bash -c \"sleep 10\"" run-process drop 1 _ send ] "1" spawn
> self '[ "bash -c \"sleep 5\"" run-process drop 2 _ send ] "2" spawn
> receive
>
> This will spawn two t
Hi John,
On 2016-11-08 22:38, John Benediktsson wrote:
> There are a lot of ways to solve the problem, but without knowing more
> about what you're looking for, I'll just leave these here.
I spent the last half hour reading your code, running it and examining
the vocabularies. Very helpful, than
On Thu, Nov 10, 2016 at 10:00 PM, wrote:
> Any
> more ideas why? Is run-process blocking everyone? Is there some FFI call
> like you mentioned? Where could I start to debug this on my own?
The only difference to what you are doing and what my test did was
you're running as a script. So I tried t
Hi Chris,
On 2016-11-10 11:03, Chris Double wrote:
> With that I see what you are seeing. Both numbers print out after the
> last thread finishes. It looks like it's buffering in this case. If I
> add a 'flush' then I see them printed after 5 seconds then 10 seconds:
>
> -8<--
11 matches
Mail list logo