From: yplan9 <yplan9@club-internet.fr>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] libutf + libregexp9
Date: Wed, 6 Feb 2008 17:19:25 +0100 [thread overview]
Message-ID: <47A9DE0D.2070408@club-internet.fr> (raw)
In-Reply-To: <20080205164755.CEF621E8C5B@holo.morphisms.net>
Hi Russ,
Thanks for the pointers.
cheers
Younès
Russ Cox a écrit :
>> Is there any examples about using "libutf" and "libregexp9"?
>>
>
> There are manual pages linked at http://swtch.com/plan9port/unix/.
>
> If you grep for regexp or rune or utf in the Plan 9 or plan9port
> source trees, you will find plenty of examples in their native
> environment. The interface is the same in the ported libraries.
>
> Here are two reasonable examples:
> http://swtch.com/usr/local/plan9/src/cmd/sed.c
> http://swtch.com/usr/local/plan9/src/cmd/unicode.c
>
> Russ
>
>
>
>
prev parent reply other threads:[~2008-02-06 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 9:27 yplan9
2008-02-05 16:47 ` Russ Cox
2008-02-06 16:19 ` yplan9 [this message]
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=47A9DE0D.2070408@club-internet.fr \
--to=yplan9@club-internet.fr \
--cc=9fans@cse.psu.edu \
/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).