From: quanstro <quanstro@gmail.com>
To: plan9port-dev@googlegroups.com
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: acme, upas commits
Date: Tue, 13 May 2014 05:23:09 -0700 [thread overview]
Message-ID: <849c2fe8-20f3-43d5-84c9-b50165958102@googlegroups.com> (raw)
In-Reply-To: <CAPavXpAmjsEjnDeQmYA7RJJQNRMsXf_ZAP5i3qtfOyYFmA1Afw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
in theory the threads that interact with regular expressions in acme
are all cooperatively scheduled. have you seen a case where they
are not? did pthreads blow up the model?
- erik
On Tuesday, May 13, 2014 7:11:02 AM UTC-4, Alexander Sychev wrote:
>
> Hi,
>
> I have commited some changes in my experimental fork of plan9port.
> https://bitbucket.org/santucco/plan9port
>
> For acme I made thread safe processing of regular expressions (actually by
> creating some context).
> For upas/nfs I made a monitoring of all mailboxes and a decoding of
> international names of mailboxes.
>
> I'm living with these changes for some time, they are working.
>
> P.S.
> By the way, new log feature is excellent, it's a time to make more
> applications for acme :-)
> --
> Best regards,
> santucco
>
--
---
You received this message because you are subscribed to the Google Groups "plan9port-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plan9port-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Type: text/html, Size: 2079 bytes --]
next prev parent reply other threads:[~2014-05-13 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 11:11 Alexander Sychev
2014-05-13 12:23 ` quanstro [this message]
2014-05-13 12:34 ` Alexander Sychev
2014-05-13 12:44 ` quanstro
2014-05-13 13:34 ` Alexander Sychev
2014-05-13 13:58 ` quanstro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=849c2fe8-20f3-43d5-84c9-b50165958102@googlegroups.com \
--to=quanstro@gmail.com \
--cc=9fans@9fans.net \
--cc=plan9port-dev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).