[DVIPDFMx] recent changes in xdvipdfmx

[Jin-Hwan Cho]

I wrote it.

>> #define strdup(s1) (char *) MEM_ADD(strdup(s1))

It was just for debugging purpose to find memory leaks. Sorry if it bothers you.

ChoF.

On Mar 31, 2010, at 6:45 PM, Peter Breitenlohner wrote:

> On Tue, 30 Mar 2010, Karl Berry wrote:
> 
>>   the recent changes in xdvipdfmx (from mathias?)
>> 
>> ChoF sent me the patch.  I don't know whether he or Matthias actually
>> wrote the code.
>> 
>>  #define strdup(s1) (char *) MEM_ADD(strdup(s1))
>> 
>> Clearly a bad mistake.
>> 
>>   Actually strdup() is only used three times in src/dpxfile.c, thus I'd
>>   suggest to replace these with mystrdup(), defined similarly as mstrdup()
>>   in fontmap.c. Wdyt?
>> 
>> Definitely.  And please send the diff back
>> To: dvipdfmx at ktug.or.kr, jonathan at jfkew.plus.com
> 
> Hi,
> 
> the recent xdvipdfmx changes have caused lots of compiler warnings, because
> you #define strdup, redefining a #define in the GNU C lib system headers. Attached is the additional change I have applied (TL SVN r17640) to avoid
> this.
> 
> Would it be possible to have a ChangeLog entry for your mods?
> 
> Shouldn't analogous mods be applied to dvipdfmx?  As long as this is kept I'd
> prefer that dvipdfmx and xdvipdfmx don't diverge any further.
> 
> Regards
> Peter Breitenlohner <peb at mppmu.mpg.de><xdvipdfmx-patch.txt>_______________________________________________
> dvipdfmx mailing list
> dvipdfmx at ktug.or.kr
> http://project.ktug.or.kr/mailman/listinfo/dvipdfmx