Re: [pdf-devel] type 3 functions

[jemarch]

Hello.

   The occurence of function objects in a type 3 function 
   dictionary makes pdf_func_t into a recursive data type.
   How is such an pdf_ obj_t constructed in the first place? 

The constructors for the several object types always takes non-object
arguments (the stream is an exception, and makes a copy of the
dict object):

pdf_obj_t pdf_create_null (void);
pdf_obj_t pdf_create_boolean (int value);
pdf_obj_t pdf_create_integer (int value);
pdf_obj_t pdf_create_real (float value);
pdf_obj_t pdf_create_string (unsigned char *value, int size);
pdf_obj_t pdf_create_name (unsigned char *value, int size);
pdf_obj_t pdf_create_array (void);
pdf_obj_t pdf_create_dict (void);
pdf_obj_t pdf_create_indirect (unsigned int on, unsigned int gn);
pdf_obj_t pdf_create_stream (pdf_obj_t dict, pdf_stm_t stm,
                             pdf_stm_pos_t data);

The constructor of the stream object could be changed to share the
same dictionary object with the caller.

Then, objects able to contain another objects (namely arrays and
dictionaries) are created empty. The functions that adds elements to
arrays and dictionaries do not make a copy of the inserted objects.

   Afaik, pdf_obj_t constructors make deep copies of their 
   arguments. 

Only for strings and names. I will change it in my next cvs commit.

--
Jose E. Marchesi  <address@hidden>
                  <address@hidden>

GNU Spain         http://es.gnu.org
GNU Project       http://www.gnu.org