From noreply at sourceforge.net Sat Aug 5 19:06:52 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Aug 2006 10:06:52 -0700 Subject: [Expat-bugs] [ expat-Patches-1523242 ] Patch to compile EXPAT with Open Watcom 1.5 Message-ID: Patches item #1523242, was opened at 2006-07-15 21:41 Message generated for change (Settings changed) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1523242&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Feature Request Status: Open >Resolution: Accepted Priority: 5 Submitted By: MikeG (greenemk) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to compile EXPAT with Open Watcom 1.5 Initial Comment: The attached archive contains the following: watcomconfig.h Open Watcom header file, copy to lib directory expat.diff Source diffs against 7-10-06 cvs watcom.zip Open Watcom makefiles, unzips to root expat directory (expat-2.0.0\watcom) Allows expat library and files to be compiled with Open Watcom 1.5 (www.openwatcom.org) for OS/2-ECS, NT/Win2000, and Linux. All tests pass on all 3 OSs. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-05 13:06 Message: Logged In: YES user_id=290026 Patch applied on Aug. 5, 2006. ---------------------------------------------------------------------- Comment By: MikeG (greenemk) Date: 2006-07-16 15:19 Message: Logged In: YES user_id=1390255 A quick change to makefile.mif. When building makefile.mif includes buildopts.inc and watopts.tmp. I moved watopts.tmp to be included after buildopts.inc so compile options can be overridden if expat is being compile as part of a larger project. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1523242&group_id=10127 From noreply at sourceforge.net Mon Aug 7 02:02:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 06 Aug 2006 17:02:28 -0700 Subject: [Expat-bugs] [ expat-Bugs-1535603 ] Error testing expat 2.0.0 Message-ID: Bugs item #1535603, was opened at 2006-08-07 02:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1535603&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pierre (pierre42) Assigned to: Nobody/Anonymous (nobody) Summary: Error testing expat 2.0.0 Initial Comment: # make check gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests.o -c tests/runtests.c gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/chardata.o -c tests/chardata.c gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/minicheck.o -c tests/minicheck.c /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests tests/runtests.o tests/chardata.o tests/minicheck.o libexpat.la g++ -s -O3 -march=i686 -c -o tests/runtestspp.o tests/runtestspp.cpp In file included from tests/runtestspp.cpp:6: tests/runtests.c: In function `void test_line_number_after_parse()': tests/runtests.c:410: error: `XML_Size' undeclared (first use this function) tests/runtests.c:410: error: (Each undeclared identifier is reported only once for each function it appears in.) tests/runtests.c:410: error: expected `;' before "lineno" tests/runtests.c:414: error: `lineno' undeclared (first use this function) tests/runtests.c: In function `void test_column_number_after_parse()': tests/runtests.c:428: error: `XML_Size' undeclared (first use this function) tests/runtests.c:428: error: expected `;' before "colno" tests/runtests.c:432: error: `colno' undeclared (first use this function) tests/runtests.c: In function `void test_line_number_after_error()': tests/runtests.c:514: error: `XML_Size' undeclared (first use this function) tests/runtests.c:514: error: expected `;' before "lineno" tests/runtests.c:518: error: `lineno' undeclared (first use this function) tests/runtests.c: In function `void test_column_number_after_error()': tests/runtests.c:534: error: `XML_Size' undeclared (first use this function) tests/runtests.c:534: error: expected `;' before "colno" tests/runtests.c:538: error: `colno' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_1()': tests/runtests.c:1230: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_2()': tests/runtests.c:1244: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_3()': tests/runtests.c:1261: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) make: *** [tests/runtestspp.o] Error 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1535603&group_id=10127 From noreply at sourceforge.net Tue Aug 8 15:35:40 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 06:35:40 -0700 Subject: [Expat-bugs] [ expat-Bugs-1536684 ] 'make check' fails for Expat 2.0.0 Message-ID: Bugs item #1536684, was opened at 2006-08-08 06:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1536684&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Test Required Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: 'make check' fails for Expat 2.0.0 Initial Comment: When I run 'make check', it returns an error saying make: CXX@: Command not found make: *** [tests/runtestspp.o] Error 127 The configure command does not provide CXX option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1536684&group_id=10127 From noreply at sourceforge.net Tue Aug 8 16:46:44 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 07:46:44 -0700 Subject: [Expat-bugs] [ expat-Bugs-1535603 ] Error testing expat 2.0.0 Message-ID: Bugs item #1535603, was opened at 2006-08-06 20:02 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1535603&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pierre (pierre42) Assigned to: Nobody/Anonymous (nobody) Summary: Error testing expat 2.0.0 Initial Comment: # make check gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests.o -c tests/runtests.c gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/chardata.o -c tests/chardata.c gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/minicheck.o -c tests/minicheck.c /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -s -O3 -march=i686 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests tests/runtests.o tests/chardata.o tests/minicheck.o libexpat.la g++ -s -O3 -march=i686 -c -o tests/runtestspp.o tests/runtestspp.cpp In file included from tests/runtestspp.cpp:6: tests/runtests.c: In function `void test_line_number_after_parse()': tests/runtests.c:410: error: `XML_Size' undeclared (first use this function) tests/runtests.c:410: error: (Each undeclared identifier is reported only once for each function it appears in.) tests/runtests.c:410: error: expected `;' before "lineno" tests/runtests.c:414: error: `lineno' undeclared (first use this function) tests/runtests.c: In function `void test_column_number_after_parse()': tests/runtests.c:428: error: `XML_Size' undeclared (first use this function) tests/runtests.c:428: error: expected `;' before "colno" tests/runtests.c:432: error: `colno' undeclared (first use this function) tests/runtests.c: In function `void test_line_number_after_error()': tests/runtests.c:514: error: `XML_Size' undeclared (first use this function) tests/runtests.c:514: error: expected `;' before "lineno" tests/runtests.c:518: error: `lineno' undeclared (first use this function) tests/runtests.c: In function `void test_column_number_after_error()': tests/runtests.c:534: error: `XML_Size' undeclared (first use this function) tests/runtests.c:534: error: expected `;' before "colno" tests/runtests.c:538: error: `colno' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_1()': tests/runtests.c:1230: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_2()': tests/runtests.c:1244: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) tests/runtests.c: In function `void test_ns_prefix_with_empty_uri_3()': tests/runtests.c:1261: error: `XML_ERROR_UNDECLARING_PREFIX' undeclared (first use this function) make: *** [tests/runtestspp.o] Error 1 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-08 10:46 Message: Logged In: YES user_id=290026 Works fine for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1535603&group_id=10127 From noreply at sourceforge.net Tue Aug 8 16:47:20 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 07:47:20 -0700 Subject: [Expat-bugs] [ expat-Bugs-1536684 ] 'make check' fails for Expat 2.0.0 Message-ID: Bugs item #1536684, was opened at 2006-08-08 09:35 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1536684&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Test Required Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: 'make check' fails for Expat 2.0.0 Initial Comment: When I run 'make check', it returns an error saying make: CXX@: Command not found make: *** [tests/runtestspp.o] Error 127 The configure command does not provide CXX option. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-08 10:47 Message: Logged In: YES user_id=290026 Works fine for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1536684&group_id=10127 From noreply at sourceforge.net Tue Aug 8 16:48:55 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 07:48:55 -0700 Subject: [Expat-bugs] [ expat-Bugs-1526052 ] '<' char in argument string? Message-ID: Bugs item #1526052, was opened at 2006-07-20 13:56 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1526052&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 7 Submitted By: Davar Learn (davarlearn) Assigned to: Nobody/Anonymous (nobody) Summary: '<' char in argument string? Initial Comment: This may be a problem with the parser, or it may be me trying to go further than XML Standards? im trying to store keyboard mapping data in arguments. Here is some sample XML code using test data: # problem here ... ... ... In this line the parser takes the '<' char to be the start of the next tag, all further tags are mis aligned and my handler ignores them as invalid data format. this may be how the program is ment to operate? If it is, are there any other ways i can store a string containing '<' characters. I need to be able to use all asci(possibly some non asci) char's to store font conversion mappings. Im working on a sourceforge project and would be greatfull of some feadback. thanks for youre help James ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-08 10:48 Message: Logged In: YES user_id=290026 Not a bug, just an error in the document. Closing this issue. ---------------------------------------------------------------------- Comment By: Myron Turner (turnermm) Date: 2006-07-20 22:59 Message: Logged In: YES user_id=771029 The parser expects src="<" This will be converted back to '<' by the parser in the output. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1526052&group_id=10127 From noreply at sourceforge.net Tue Aug 8 16:49:31 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 07:49:31 -0700 Subject: [Expat-bugs] [ expat-Bugs-1515600 ] Segfault after removing character data handler Message-ID: Bugs item #1515600, was opened at 2006-07-01 13:21 Message generated for change (Settings changed) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1515600&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None >Group: Test Required Status: Open Resolution: Fixed Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Nobody/Anonymous (nobody) Summary: Segfault after removing character data handler Initial Comment: Removing the character data handler from within the character data handler while character data remains to be reported causes a call to a NULL pointer (generally followed by a memory access violation of your platform's favorite flavor). If the XML_StopParser() API has been called, this is not a problem with the version in CVS. This is admittedly an odd use case. The recent fixes to make the XML_StopParser() calls supported makes the parser behave well when accessed from languages that support exceptions (the host language API can call XML_StopParser to abort further work from Expat when an exception occurs). The case of a character data handler removing itself is unusual (in context, there can be no calls to anything else other than a decoding handler). I think there are two possible solutions: 1) Document that the character data handler cannot remove itself without calling XML_StopParser(). This avoids introducing a performance penalty for really this really odd case, but I don't know how bad testing for a NULL value would really be at this point, since there are a few other checks and an indirect assignment. 2) Add a check that the character data handler is still set before the loop goes around again, and fall back to the defaultHandler for the remaining data. This would introduce a single check for a NULL pointer in the loop in the XML_TOK_DATA_CHARS case in doContent(). I've attached a patch with a test case that demonstrates this bug; the test generates a segfault on Unix. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-07-10 15:03 Message: Logged In: YES user_id=290026 Applied an improved patch that preserves default handler failover logic. See xmlparse.c rev. 1.158. Docs updated as well. Python compatibility still needs testing. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-07-05 09:09 Message: Logged In: YES user_id=290026 Applied patch in xmlparse.c rev. 1.156 and reference.html rev. 1.71. Please let nme know if we should discuss special treatment of aborting vs. suspending. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-07-04 13:42 Message: Logged In: YES user_id=290026 I replaced my last attachment with one that includes an update to the docs (reference.html). This solution should fix issue # 1515266 as well. I intend to commit this soon, if no objections are made. Note to Fred: I took out your test for XML_FINISHED and XML_SUSPENDED, as it currently introduces an issue for XML_SUSPENDED, and inconsistent behaviour for XML_FINISHED. We can discuss special treatment of aborting vs. suspending (i.e. ensure no more call-backs when aborting) later, but even as it is, subsequent call-backs can be suppressed by setting the affected handlers to NULL. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-07-04 09:55 Message: Logged In: YES user_id=290026 The same issue also exists in the doCdataSection() function, and I think the solution I suggested (putting the check if the character data handler is set into the internal loop) also solves bug # 1515266, as I described there. For the case where there is only one call-back, this should not be a performance penalty at all, as there still would be only one check if the handler is set. Attached as xmlparse.c.diff (Internal loop solution) - this also fixes the doCdataSection() function. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-07-03 16:40 Message: Logged In: YES user_id=290026 I think in most cases this is not a problem. The general parsing loop in doContent() always checks if the characterDataHandler is set first. In the specific case you mentioned, there is a loop within the general loop, and in that internal loop there is no check for NULL. We could, for instance, pull the NULL check inside the loop, like your 2nd case, and the result would look like this: case XML_TOK_DATA_CHARS: if (MUST_CONVERT(enc, s)) { for (;;) { if (characterDataHandler) { ICHAR *dataPtr = (ICHAR *)dataBuf; XmlConvert(enc, &s, next, &dataPtr, (ICHAR *)dataBufEnd); *eventEndPP = s; characterDataHandler(handlerArg, dataBuf, (int)(dataPtr - (ICHAR *)dataBuf)); if (s == next) break; *eventPP = s; } } } else if (characterDataHandler) { characterDataHandler(handlerArg, (XML_Char *)s, (int)((XML_Char *)next - (XML_Char *)s)); } else if (defaultHandler) reportDefault(parser, enc, s, next); break; I am not sure if the performance penalty is that high. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1515600&group_id=10127 From noreply at sourceforge.net Sat Aug 19 22:58:37 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Aug 2006 13:58:37 -0700 Subject: [Expat-bugs] [ expat-Bugs-1543233 ] bug in examples/outline.c Message-ID: Bugs item #1543233, was opened at 2006-08-19 20:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1543233&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Imran (imranghory) Assigned to: Nobody/Anonymous (nobody) Summary: bug in examples/outline.c Initial Comment: In examples/outline.c XML_ParserFree() isn't called to free the parser, hence causing a memory leak. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1543233&group_id=10127 From noreply at sourceforge.net Mon Aug 28 22:58:27 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 28 Aug 2006 13:58:27 -0700 Subject: [Expat-bugs] [ expat-Bugs-1548182 ] MinGW 'FASTCALL' problem (and how to fix it) Message-ID: Bugs item #1548182, was opened at 2006-08-28 22:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1548182&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Sebastian Pipping (hartwork) Assigned to: Nobody/Anonymous (nobody) Summary: MinGW 'FASTCALL' problem (and how to fix it) Initial Comment: Compiling Expat 2.0.0 with MinGW gives a '"FASTCALL" redefined' warning. This can be fixed by changing line 23 in file "expat_internal.h": --- #if defined(__GNUC__) && defined(__i386__) +++ #if defined(__GNUC__) && defined(__i386__) && !defined(__MINGW32__) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1548182&group_id=10127 From noreply at sourceforge.net Wed Aug 30 16:53:22 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 30 Aug 2006 07:53:22 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 07:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 From noreply at sourceforge.net Wed Aug 30 18:08:38 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 30 Aug 2006 09:08:38 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 10:53 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-30 12:08 Message: Logged In: YES user_id=290026 The atts argument to start handler is a null terminated array of char* pointers. If it is empty, the first entry is null. Seems OK to me, not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 From noreply at sourceforge.net Thu Aug 31 11:08:16 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 31 Aug 2006 02:08:16 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 07:53 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 02:08 Message: Logged In: NO aren't you afraid to have a memory leak with this method? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-30 09:08 Message: Logged In: YES user_id=290026 The atts argument to start handler is a null terminated array of char* pointers. If it is empty, the first entry is null. Seems OK to me, not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 From noreply at sourceforge.net Thu Aug 31 15:02:54 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 31 Aug 2006 06:02:54 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 10:53 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-31 09:02 Message: Logged In: YES user_id=290026 Why? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 05:08 Message: Logged In: NO aren't you afraid to have a memory leak with this method? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-30 12:08 Message: Logged In: YES user_id=290026 The atts argument to start handler is a null terminated array of char* pointers. If it is empty, the first entry is null. Seems OK to me, not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 From noreply at sourceforge.net Thu Aug 31 17:04:12 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 31 Aug 2006 08:04:12 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 07:53 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 08:04 Message: Logged In: NO how you free all resources in atts array? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-31 06:02 Message: Logged In: YES user_id=290026 Why? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 02:08 Message: Logged In: NO aren't you afraid to have a memory leak with this method? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-30 09:08 Message: Logged In: YES user_id=290026 The atts argument to start handler is a null terminated array of char* pointers. If it is empty, the first entry is null. Seems OK to me, not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 From noreply at sourceforge.net Thu Aug 31 22:09:44 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 31 Aug 2006 13:09:44 -0700 Subject: [Expat-bugs] [ expat-Bugs-1549343 ] start handler atts value null ? Message-ID: Bugs item #1549343, was opened at 2006-08-30 10:53 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: start handler atts value null ? Initial Comment: When the atts value in xml is null, the atts value in start handler is not null, the atts[0] is null and other atts value, per exemple atts[1] is the same value of the last value... its normal ? ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-31 16:09 Message: Logged In: YES user_id=290026 Expat takes care of that, you don't need to worry. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 11:04 Message: Logged In: NO how you free all resources in atts array? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-31 09:02 Message: Logged In: YES user_id=290026 Why? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-08-31 05:08 Message: Logged In: NO aren't you afraid to have a memory leak with this method? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-08-30 12:08 Message: Logged In: YES user_id=290026 The atts argument to start handler is a null terminated array of char* pointers. If it is empty, the first entry is null. Seems OK to me, not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1549343&group_id=10127