[poppler] GooString ‹ Why do we use it instead of std::string?
Albert Astals Cid
aacid at kde.org
Fri Nov 4 06:01:27 PDT 2011
A Dijous, 3 de novembre de 2011, Josh Richardson vàreu escriure:
> I noticed that there is some use of std::string in the codebase. I think
> GooString is historical, but it does provide some number conversion
> facilities that are a little less straightforward with std::string. For
> the most part GooString has met my needs for pdftohtml, and where it
> hasn't, I've extended it, because for consistency it seems like a good
> choice -- don't know if that's right or wrong. It's a good question.
The general answer is, for poppler core code, use GooString since it probably
has what you want and it gives consistency, for pdftohtml-only code feel free
to use whatever you want.
Albert
>
> --josh
>
> On 11/3/11 10:43 PM, "Alec Taylor" <alec.taylor6 at gmail.com> wrote:
> >Good evening,
> >
> >Why should I use GooString instead of std::string?
> >
> >I've been very careful so far with my patches to only using GooString.
> >But I was wondering if there is a specific added feature set (i.e.
> >UTF16) which can only be achieved with your custom GooString library.
> >
> >Thanks for all information,
> >
> >Alec Taylor
> >_______________________________________________
> >poppler mailing list
> >poppler at lists.freedesktop.org
> >http://lists.freedesktop.org/mailman/listinfo/poppler
>
> _______________________________________________
> poppler mailing list
> poppler at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/poppler
More information about the poppler
mailing list