On Mar 5, 2008, at 1:03 AM, Jens Alfke wrote:
On 4 Mar '08, at 8:55 PM, John Engelhart wrote:
The ICU Regex C API (the one I need to use for RegexKit, not the C+
+ one, which I haven't really looked at) is very multi-threading
unfriendly. Basically, the 'compiled' regex, the string being
On 4 Mar '08, at 8:55 PM, John Engelhart wrote:
It's sort of ambiguous if the /usr/lib/libicucore library is
'supported' or not. I believe the general consensus is that it's
not really there for public use, hence the missing headers, but it's
also not verboten.
Yeah, this is annoying. I
On Mar 4, 2008, at 12:50 PM, Jens Alfke wrote:
On 4 Mar '08, at 3:25 AM, Jonathan Dann wrote:
That is a seriously good framework, and the documentation is great
too.
My only issue with regexkit is that it uses PCRE instead of ICU.
[disclosure: I am the author of RegexKit]
Hard to make e
On Mar 4, 2008, at 11:50 AM, Jens Alfke wrote:
On 4 Mar '08, at 3:25 AM, Jonathan Dann wrote:
That is a seriously good framework, and the documentation is great
too.
My only issue with regexkit is that it uses PCRE instead of ICU.
PCRE has to be compiled into the library, making it large
On 4 Mar '08, at 10:19 AM, Jonathan Dann wrote:
I'm most-likely going to have to support many text-encodings. Say
if I'm writing a document in Jaspanese (Mac OS), will I have to
convert that to UTF-8 before the methods of something like RegexKit
would work? Any caveats you know of that I
On 4 Mar 2008, at 17:50, Jens Alfke wrote:
On 4 Mar '08, at 3:25 AM, Jonathan Dann wrote:
That is a seriously good framework, and the documentation is great
too.
My only issue with regexkit is that it uses PCRE instead of ICU.
PCRE has to be compiled into the library, making it larger (w
On 4 Mar '08, at 3:25 AM, Jonathan Dann wrote:
That is a seriously good framework, and the documentation is great
too.
My only issue with regexkit is that it uses PCRE instead of ICU.
PCRE has to be compiled into the library, making it larger (whereas
ICU is already built into the OS.)
