Author: Graycode Date: To: pcre-dev Subject: Re: [pcre-dev] [Bug 1049] Add support for UTF-16
> Single or dual library? >
> At the moment we have two libraries: libpcre and libpcre16. It was essential
> when the library was splitted (due to testing) but I realized we could merge
> them to a single one now.
>
> Pro:
> - share tables among them, like unicode tables
> - we have a single pcre.h header as well
> Cont:
> - it feels less tidy
>
> What do you prefer?
I need to be able to build conventional 8-bit without any 16.
If (when) I someday need to use PCRE as UTF-16 then it might not
matter as much whether it was a combined library.
One detriment to a combined 8+16 library is that it may be too easy
to accidentally mis-code to the wrong 8/16 API and not have that
caught during linkage. For example we could compile a RegEx with 16
then study or free with 8 and our code might build cleanly.
I think most applications will use either 8 or 16, perhaps rare that
both versions would be used within the same program.
