[poppler] [PATCH 0/5] Various fixes relating to bug #24575

[Albert Astals Cid]

A Dissabte, 23 de gener de 2010, David A Benjamin va escriure:
> On Fri, 22 Jan 2010, Albert Astals Cid wrote:
> > A Divendres, 22 de gener de 2010, David A Benjamin va escriure:
> >> Oops. Sorry guys; forgot to set the subject.
> >
> > Sorry to be a pain, but could you try not to use GooVector, that class
> > has a "unknown" origin and we don't use anywhere other than pdftohtml and
> > i'd prefer to keep it that way.
> 
> Sure. Would GooList be preferable or should I just roll my own stack?
> (GooList is vaguely annoying in that it stores pointers. I could also
> maintain a stack of GfxState pointers stored in a GooList, but then you
> have pointers that don't retain ownership of the object and deleteGooList
> assumes they do.)

GooList would be Ok although maybe annoying for your use case.

> 
> So, what is the story with GooVector? Is it just unknown copyright?

Yes, it mentions three people in the copyright that never answered my mails 
asking to clarify	which license their file was under.

> Vectors are hardly complicated structures to implement. Making a new one
> with a much fuller interface would be trivial.

Yeah, but still somewhat time consuming. Are you volunteering to create one? 
GPL2 or later?

> (Or we could use the
> STL's... I'm not sure what libpoppler's policies are w.r.t STL usage. I
> would think it's safe to consider "portable" these days.)

Yes, i agree STL is safe to use everywhere but the poppelr core isn't using it 
and just for a small vector i'd prefer to keep not doing it.

Albert

> 
> David
> _______________________________________________
> poppler mailing list
> poppler at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/poppler
>