> Date: Fri, 23 Jan 2009 00:53:39 +0100 > From: [email protected] > > > > Gerel, what do you think about this? We would of course loose the > > > benefits of the opaque pointers in this case, but > 'pdf_obj_equal_p' > > > throwing PDF_ENOMEM sounds quite weird, and I think that we > could make an > > > exception and publish the iterator structure. > > > > > > > BTW An alternative would be to allocate an iterator along with the > > list, and still have the structures hidden from the public. What > > you think ? > > > > Hm, a pre-allocated iterator... but then we would need to update the > > module interface to allow the client to get a reference to it, right? > > > > Jemarch, I'm confused now :-), let's restate the issue or let it die. > > :''D > > I had a quite intensive working "day" (including a large part of the > last night) and my poor limited brain is more damaged than usual. > > Can you explain your suggestion, but this time for dummies? :)
Jemarch you can read my last response to Michael, I hope that clear things up for you. BTW I won't make any changes to the code until we get the Object layer design and brainstorm complete and a task for the lexer/parser is open. Let's keep to the development procedures, please. regards, -gerel
