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

[David A Benjamin]

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.)

So, what is the story with GooVector? Is it just unknown copyright? 
Vectors are hardly complicated structures to implement. Making a new one 
with a much fuller interface would be trivial. (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.)

David