From webpurchasing at yahoo.com Tue Nov 8 03:45:17 2005 From: webpurchasing at yahoo.com (Zhan Zhaohua) Date: Mon, 7 Nov 2005 18:45:17 -0800 (PST) Subject: [Expat-discuss] Some Question about license Message-ID: <20051108024517.21725.qmail@web52104.mail.yahoo.com> Dear: Our organization is planning a big project which is a Linux-Embedded system and will be sold as products in the market. Through our investigation, We want to use expat at our system. But when we investigate the license of FF we met some trouble. We know the when we compiling the expat, we couldn't need any software. Is it correct? And we couldn't find which is necessary for usage.So which is necessary for the expat usage? Whether we only need to add the MIT License at our product ? Don't be concerned about the expat requirement? if meet this condition: The A is requirement of Expat, and the B is requirement of the A. Whether we add the B license at product when we use the expat? This is first time for us to build so big project. We don't want to make a mistake at license, it will cause more trouble for our organization. Maybe Those of questions are not suitable, but any informations will help us a lot. Thank you very much again! Wish a successful further cooperation! Best regards Zhan Zhaohua 2005.11.8 __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com From ofi at mymail.ch Tue Nov 15 14:29:56 2005 From: ofi at mymail.ch (ofi) Date: Tue, 15 Nov 2005 14:29:56 +0100 Subject: [Expat-discuss] (no subject) Message-ID: <380-2200511215132956312@mymail.ch> hi everybody, actually i'm using libexpat.so.0.5.0 under red hat 6.2. i want du parse an xml-file that contains many text-fields und german language, so der can be some "special characters" for example like an ?. i tried to encode this character like this  but when i parse thru it the function (set in XML_SetCharacterDataHandler) gets 2 characters. the first one is 194 (0xC2) and then the correct one 129 (0x81). so for mit it looks like a problem with the encoding (some sort of UTF encoding). so i also tried to set "ISO-8859-1" as encoding when i call the XML_ParserCreate function, but this has the same effect. has anybody an other idea to get only one character with the ASCII code 129?? ___________________________________________________________________________ mymail - der unschlagbare und kostenlose E-Mail-Dienst der Schweiz! http://mymail.ch/?redirect=9999 Bei uns finden Sie trendige Geschenkideen und Wohnaccessoires! http://mymail.ch/?redirect=1610 From ofi at mymail.ch Tue Nov 15 14:50:36 2005 From: ofi at mymail.ch (ofi) Date: Tue, 15 Nov 2005 14:50:36 +0100 Subject: [Expat-discuss] Special Character encoding Message-ID: <380-2200511215135036671@mymail.ch> hi everybody, actually i'm using libexpat.so.0.5.0 under red hat 6.2. i want du parse an xml-file that contains many text-fields und german language, so der can be some "special characters" for example like an ?. i tried to encode this character like this  but when i parse thru it the function (set in XML_SetCharacterDataHandler) gets 2 characters. the first one is 194 (0xC2) and then the correct one 129 (0x81). so for mit it looks like a problem with the encoding (some sort of UTF encoding). so i also tried to set "ISO-8859-1" as encoding when i call the XML_ParserCreate function, but this has the same effect. has anybody an other idea to get only one character with the ASCII code 129?? ____________________________________________________________________________ ________ mymail - der unschlagbare und kostenlose E-Mail-Dienst der Schweiz! http://mymail.ch/?redirect=9999 Der neue Opel Zafira. Sichern Sie sich Ihren Preisvorteil f?r Schnell-Entschlossene. http://mymail.ch/?redirect=2138 From santosh.yatnatti at gmail.com Wed Nov 23 10:13:51 2005 From: santosh.yatnatti at gmail.com (Santosh Yatnatti) Date: Wed, 23 Nov 2005 14:43:51 +0530 Subject: [Expat-discuss] Query on foot print.. Message-ID: <18bdaa990511230113l1782fa78jb64796f12747fc36@mail.gmail.com> Hi, How can I reduce size of libexpat.lib library? I tried using XML_MIN_SIZE flag and minimize option in VC++, size is reduced to 136KB. But i still need less size with minimum functionality. Any help/suggestion/comment are greatly appreciated. Thanks in advance, Santosh From karl at waclawek.net Thu Nov 24 03:43:27 2005 From: karl at waclawek.net (Karl Waclawek) Date: Wed, 23 Nov 2005 21:43:27 -0500 Subject: [Expat-discuss] Query on foot print.. In-Reply-To: <18bdaa990511230113l1782fa78jb64796f12747fc36@mail.gmail.com> References: <18bdaa990511230113l1782fa78jb64796f12747fc36@mail.gmail.com> Message-ID: <438528CF.6090206@waclawek.net> Santosh Yatnatti wrote: >Hi, >How can I reduce size of libexpat.lib library? >I tried using XML_MIN_SIZE flag and minimize option in VC++, >size is reduced to 136KB. >But i still need less size with minimum functionality. >Any help/suggestion/comment are greatly appreciated. > > Check out this old post: http://mail.libexpat.org/pipermail/expat-discuss/2004-April/001380.html Karl From santosh.yatnatti at gmail.com Thu Nov 24 06:36:14 2005 From: santosh.yatnatti at gmail.com (Santosh Yatnatti) Date: Thu, 24 Nov 2005 11:06:14 +0530 Subject: [Expat-discuss] Query on foot print.. In-Reply-To: <438528CF.6090206@waclawek.net> References: <18bdaa990511230113l1782fa78jb64796f12747fc36@mail.gmail.com> <438528CF.6090206@waclawek.net> Message-ID: <18bdaa990511232136u71c289ecrdde30aedfa1f94c9@mail.gmail.com> Hi Karl, With those settings what you had given, size is still 136 KB.. Is there anyother way to make it still smaller? Thanks, Santosh On 11/24/05, Karl Waclawek wrote: > > Santosh Yatnatti wrote: > > >Hi, > >How can I reduce size of libexpat.lib library? > >I tried using XML_MIN_SIZE flag and minimize option in VC++, > >size is reduced to 136KB. > >But i still need less size with minimum functionality. > >Any help/suggestion/comment are greatly appreciated. > > > > > Check out this old post: > > http://mail.libexpat.org/pipermail/expat-discuss/2004-April/001380.html > > Karl > From karl at waclawek.net Thu Nov 24 15:39:07 2005 From: karl at waclawek.net (Karl Waclawek) Date: Thu, 24 Nov 2005 09:39:07 -0500 Subject: [Expat-discuss] Query on foot print.. In-Reply-To: <18bdaa990511232136u71c289ecrdde30aedfa1f94c9@mail.gmail.com> References: <18bdaa990511230113l1782fa78jb64796f12747fc36@mail.gmail.com> <438528CF.6090206@waclawek.net> <18bdaa990511232136u71c289ecrdde30aedfa1f94c9@mail.gmail.com> Message-ID: <4385D08B.2080206@waclawek.net> Santosh Yatnatti wrote: > Hi Karl, > With those settings what you had given, size is still 136 KB.. > Is there anyother way to make it still smaller? > Thanks, > Santosh I specified XML_MIN_SIZE in the project properties and commented out the defines for XML_DTD, XML_NS and XML_CONTEXT_BYTES in winconfig.h, and got 128KB. None of the project settings to minimize code size made a difference. Actually, XML_MIN_SIZE does not seem to have an effect when specified as project setting, but if you define it in winconfig.h, it works. I got it down to 108 KB. Hope that helps, Karl From maratbn at yahoo.com Thu Nov 24 20:03:18 2005 From: maratbn at yahoo.com (Marat BN) Date: Thu, 24 Nov 2005 11:03:18 -0800 (PST) Subject: [Expat-discuss] Question about the libexpat character data handler automatic escape sequence decoding. Message-ID: <20051124190318.51410.qmail@web53703.mail.yahoo.com> Hi, I have a question regarding the libexpat character data handler callback function that's set via libexpat API method XML_SetCharacterDataHandler(...) I noticed that by default libexpat decodes the XML escape sequences from text being parsed before passing them to the character data handler. -- If the XML string being parsed contains XML escape sequences, such as > < & &#xxxx; etc, then the XML_Char * string provided to the character data handler will have all these escape sequences decoded. libexpat must be automatically doing this decoding internally. In my application, I would like to receive the escape sequences intact. Does anyone know how to prevent the character data handler from automatically decoding the XML escape sequences? Or is there another separate data handler callback function that leaves the escape sequences intact? On a related issue -- does libexpat have a separate API to encode/decode XML escape sequences? Thanks, Marat __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From nickmacd at gmail.com Thu Nov 24 22:25:32 2005 From: nickmacd at gmail.com (Nick MacDonald) Date: Thu, 24 Nov 2005 16:25:32 -0500 Subject: [Expat-discuss] Question about the libexpat character data handler automatic escape sequence decoding. In-Reply-To: <20051124190318.51410.qmail@web53703.mail.yahoo.com> References: <20051124190318.51410.qmail@web53703.mail.yahoo.com> Message-ID: Well the obvious answer, which you may not like, would be to assume that those escaped characters could never "occur naturally" so if you want, just reconvert them back after receiving them in the XML_SetCharacterDataHandler(). On 11/24/05, Marat BN wrote: > > I have a question regarding the libexpat character > data handler callback > function that's set via libexpat API method > XML_SetCharacterDataHandler(...) > > I noticed that by default libexpat decodes the XML > escape sequences from > text being parsed before passing them to the character > data handler. -- If > the XML string being parsed contains XML escape > sequences, such as > < > & &#xxxx; etc, then the XML_Char * string provided > to the character data > handler will have all these escape sequences decoded. > libexpat must be > automatically doing this decoding internally. > > In my application, I would like to receive the escape > sequences intact. > Does anyone know how to prevent the character data > handler from > automatically decoding the XML escape sequences? Or > is there another > separate data handler callback function that leaves > the escape sequences > intact? > > On a related issue -- does libexpat have a separate > API to encode/decode XML > escape sequences? > -- Nick MacDonald NickMacD at gmail.com From maratbn at yahoo.com Thu Nov 24 22:42:57 2005 From: maratbn at yahoo.com (Marat BN) Date: Thu, 24 Nov 2005 13:42:57 -0800 (PST) Subject: [Expat-discuss] Question about the libexpat character data handler automatic escape sequence decoding. Message-ID: <20051124214257.42876.qmail@web53704.mail.yahoo.com> Yep, that's what I'm doing right now, but you're right, I don't like this decoding and then re-encoding because that's not using the processing power efficiently. ----- Original Message ----- From: Nick MacDonald To: Marat BN Cc: expat-discuss at libexpat.org Sent: Thursday, November 24, 2005 1:25 PM Subject: Re: [Expat-discuss] Question about the libexpat character data handler automatic escape sequence decoding. Well the obvious answer, which you may not like, would be to assume that those escaped characters could never "occur naturally" so if you want, just reconvert them back after receiving them in the XML_SetCharacterDataHandler(). On 11/24/05, Marat BN wrote: I have a question regarding the libexpat character data handler callback function that's set via libexpat API method XML_SetCharacterDataHandler(...) I noticed that by default libexpat decodes the XML escape sequences from text being parsed before passing them to the character data handler. -- If the XML string being parsed contains XML escape sequences, such as > < & &#xxxx; etc, then the XML_Char * string provided to the character data handler will have all these escape sequences decoded. libexpat must be automatically doing this decoding internally. In my application, I would like to receive the escape sequences intact. Does anyone know how to prevent the character data handler from automatically decoding the XML escape sequences? Or is there another separate data handler callback function that leaves the escape sequences intact? On a related issue -- does libexpat have a separate API to encode/decode XML escape sequences? -- Nick MacDonald NickMacD at gmail.com --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free. From rahim at easydevices.co.uk Fri Nov 25 14:22:49 2005 From: rahim at easydevices.co.uk (Rahim @ Easy Devices.co.uk) Date: Fri, 25 Nov 2005 13:22:49 -0000 Subject: [Expat-discuss] NEED HELP PARSE XML IN PHP FILE Message-ID: Hello , I have some question to ask. 1. Can i parse an xml file having a php file. 2. Where should i keep the .xml file in the directory 3. Can u send an example running xml file using php. 4. Please if u can give me the readme file to install the expat using php with all the necessary details. your early reply will be appreciable. Thanks Best regards, Abdul Rahim Khan Computer Engineer Easy Devices.co.uk Tel: 0871 7000 156 Fax: 0871 7000 159 Mobile #:00447733355291 Web: www.easydevices.co.uk Email: rahim at easydevices.co.uk ____________________________________________________________________ EMAIL DISCLAIMER This message is for the intended recipient only. It may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. If you contact us by Email, we may store your name and address to facilitate communication. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. From rahim at easydevices.co.uk Fri Nov 25 14:24:12 2005 From: rahim at easydevices.co.uk (Rahim @ Easy Devices.co.uk) Date: Fri, 25 Nov 2005 13:24:12 -0000 Subject: [Expat-discuss] (no subject) Message-ID: Hello Jam Clark, I have some question to ask. 1. Can i parse an xml file having a php file. 2. Where should i keep the .xml file in the directory 3. Can u send an example running xml file using php. 4. Please give me an example or parsing xml file through php your early reply will be appreciable. Thanks Best regards, Abdul Rahim Khan Computer Engineer Easy Devices.co.uk Tel: 0871 7000 156 Fax: 0871 7000 159 Mobile #:00447733355291 Web: www.easydevices.co.uk Email: rahim at easydevices.co.uk ____________________________________________________________________ EMAIL DISCLAIMER This message is for the intended recipient only. It may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. If you contact us by Email, we may store your name and address to facilitate communication. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. From rahim at easydevices.co.uk Fri Nov 25 14:42:57 2005 From: rahim at easydevices.co.uk (Rahim @ Easy Devices.co.uk) Date: Fri, 25 Nov 2005 13:42:57 -0000 Subject: [Expat-discuss] When i run an xml file i receive this error using PHP to open the file Message-ID: ERROR GENERATOR AFTER RUNNING THE FILE OF PHP OPENING xml file. XML error: xml declaration not at start of external entity at line 1 NOTE: PLEASE REPLY TO THIS MESSAGE AS EARLY AS IT IS POSSIBLE. Thanks Best regards, Abdul Rahim Khan Computer Engineer Easy Devices.co.uk Tel: 0871 7000 156 Fax: 0871 7000 159 Mobile #:00447733355291 Web: www.easydevices.co.uk Email: rahim at easydevices.co.uk ____________________________________________________________________ EMAIL DISCLAIMER This message is for the intended recipient only. It may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. If you contact us by Email, we may store your name and address to facilitate communication. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. From reid at x10sys.com Mon Nov 28 10:24:48 2005 From: reid at x10sys.com (Reid Spencer) Date: Mon, 28 Nov 2005 01:24:48 -0800 Subject: [Expat-discuss] When i run an xml file i receive this error using PHP to open the file In-Reply-To: References: Message-ID: <438ACCE0.7070402@x10sys.com> Rahim, Most PHP files are not semantically valid because they lack the xml declaration. Unfortunately, adding one renders the file invalid for PHP. I would recommend, if you're on Unix, that you simply use "cat" to combine the necessary header when you parse a PHP file with any XML processor. The header you are missing is: You might also want a DTD or Schema declaration next (see the XML specs for that). You can get it to parse with the Unix command line: (echo '' ; cat PHP_FILE) | XML_PARSER where you replace PHP_FILE with the php file you want parsed and XML_PARSER with any XML parser that can read its standard input (such as expat). Hope that helps. Reid Rahim @ Easy Devices.co.uk wrote: > > ERROR GENERATOR AFTER RUNNING THE FILE OF PHP OPENING xml file. > > > XML error: xml declaration not at start of external entity at line 1 > > > NOTE: > PLEASE REPLY TO THIS MESSAGE AS EARLY AS IT IS POSSIBLE. > > > Thanks > > Best regards, > > Abdul Rahim Khan > > Computer Engineer > > Easy Devices.co.uk > > Tel: 0871 7000 156 > Fax: 0871 7000 159 > Mobile #:00447733355291 > > Web: www.easydevices.co.uk > Email: rahim at easydevices.co.uk > > > ____________________________________________________________________ > EMAIL DISCLAIMER > > This message is for the intended recipient only. It may contain confidential > or proprietary information. If you receive this message in error, please > immediately delete it, destroy all copies of it and notify the sender. > You must not use or disclose any part of this message if you are not the > intended recipient. We may monitor all Email communication through our > networks. > > If you contact us by Email, we may store your name and address to facilitate > communication. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise. > > We take reasonable precautions to ensure our Emails are virus free. However, > we cannot accept responsibility for any virus transmitted by us and > recommend that you subject any incoming Email to your own virus checking > procedures. > > > _______________________________________________ > Expat-discuss mailing list > Expat-discuss at libexpat.org > http://mail.libexpat.org/mailman/listinfo/expat-discuss > From rahim_khan_2000 at yahoo.com Mon Nov 28 20:29:50 2005 From: rahim_khan_2000 at yahoo.com (ABDUL RAHIM) Date: Mon, 28 Nov 2005 11:29:50 -0800 (PST) Subject: [Expat-discuss] php_domxml.dll file is not loading to the server please help me urgently Message-ID: <20051128192950.47539.qmail@web50107.mail.yahoo.com> Hello, I am trying to load php_domxml.dll but it is giving the following error. please help me why it is not loading . I have written the following line in the httpd.conf file to load the php_domxml.dll file. LoadModule php_DomXml "c:/php/dlls/extensions/php_domxml.dll" but it is giving the below error. -------------------------------------------------------- The Apache service named reported the following error: >>> Cannot load C:/php/dlls/extensions/php_domxml.dll into server: The specified module could not be found. . For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ------------------------------------------------------------ Please mail to the following error urgently. ABDUL RAHIM KHAN SSUET,SOFTWARE ENGINEER. ADD: 12/8, Calder Drive,Edinburgh , EH114LU,SCOTLAND PHONE NO:00447733355291. ADD: 73/1F2, NICOLSON STREET,EH89BZ,EDINBURGH,SCOTLAND __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ From karl at waclawek.net Tue Nov 29 15:00:46 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 09:00:46 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? Message-ID: <438C5F0E.2020402@waclawek.net> We are trying to decide whether we should change some API return values to 64 bit integers to support file sizes > 2GB. Affected would be these API members: XML_GetCurrentByteIndex() XML_GetCurrentByteCount() XML_GetCurrentLineNumber() XML_GetCurrentColumnNumber() Obviously this requires applications to be recompiled. The question is, how "breaking" would that change be? How many applications are actually using these members? Should this be delayed after the release of Expat 2.0? Karl From pappy at vappy.com Tue Nov 29 21:26:49 2005 From: pappy at vappy.com (pappy@vappy.com) Date: Tue, 29 Nov 2005 12:26:49 -0800 Subject: [Expat-discuss] Install issues, lost expat_external.h Message-ID: ? Hi I'm trying to install expat and then the PERL /XML-Parser-2.34 after that on my AIX 5.x system with root. ? It seems as though expat installs OK, but when I go to install the XML-Parser it says it can't find the expat_external.h file (see way on the bottom). Does anybody have any idea what is going on? When I search my system for expat_external.h, it only finds it in the expat install source directory (e.g. /home/earwax/soap/expat-1.95.8/lib/expat_external.h) I would have expected expat_external.h to have been installed on the system, maybe in /usr/local/include? Output of install attempt below. ? Thanks, ? Pappy ? ? /home/earwax/soap/expat-1.95.8 # ./configure checking build system type... powerpc-ibm-aix5.1.0.0 checking host system type... powerpc-ibm-aix5.1.0.0 checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse /usr/bin/nm -B output... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... none checking if gcc static flag -static -Wl,-lC works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... aix5.1.0.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install-sh -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for gcc option to accept ANSI C... none needed checking for an ANSI C-conforming const... yes checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h /home/earwax/soap/expat-1.95.8 # Check status and if everything is OK run make as shown below ? /home/earwax/soap/expat-1.95.8 # make ??????? /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPA T_CONFIG_H?? -I./lib -I. -o lib/xmlparse.lo -c lib/xmlparse.c ??????? /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPA T_CONFIG_H?? -I./lib -I. -o lib/xmltok.lo -c lib/xmltok.c ??????? /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPA T_CONFIG_H?? -I./lib -I. -o lib/xmlrole.lo -c lib/xmlrole.c ??????? /bin/sh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_C ONFIG_H?? -I./lib -I. -no-undefined -version-info 5:0:5 -rpath /usr/local/lib? -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlr ole.lo ??????? gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H?? -I./lib -I. -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c ??????? gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H?? -I./lib -I. -o xmlwf/xmlfile. o -c xmlwf/xmlfile.c ??????? gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H?? -I./lib -I. -o xmlwf/codepage .o -c xmlwf/codepage.c ??????? gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H?? -I./lib -I. -o xmlwf/readfile map.o -c xmlwf/readfilemap.c ? ??????/bin/sh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_C ONFIG_H?? -I./lib -I.? -o xmlwf/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o libexpat.la Target "default" is up to date. /home/earwax/soap/expat-1.95.8 # If everything looks good run the make install command as shown below ? /home/earwax/soap/expat-1.95.8 # make install ??????? /bin/sh ./conftools/mkinstalldirs /usr/local/lib /usr/local/include mkdir /usr/local/include ??????? /bin/sh ./libtool --mode=install conftools/install-sh -c libexpat.la /usr/local/lib/libexpat.la conftools/install-sh -c .libs/libexpat.a /usr/local/lib/libexpat.a conftools/install-sh -c .libs/libexpat.lai /usr/local/lib/libexpat.la conftools/install-sh -c .libs/libexpat.a /usr/local/lib/libexpat.a ranlib /usr/local/lib/libexpat.a chmod 644 /usr/local/lib/libexpat.a ---------------------------------------------------------------------- Libraries have been installed in: ?? /usr/local/lib ? If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: ?? - add LIBDIR to the `LIBPATH' environment variable ???? during execution ?? - use the `-Wl,-bnolibpath -Wl,-blibpath:LIBDIR:/usr/lib:/lib' linker flag ? See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- ??????? conftools/install-sh -c -m 644 ./lib/expat.h ./lib/expat_external.h /usr/local/include ??????? /bin/sh ./conftools/mkinstalldirs /usr/local/bin /usr/local/man/man1 ??????? /bin/sh ./libtool --mode=install conftools/install-sh -c xmlwf/xmlwf /usr/local/bin/xmlwf conftools/install-sh -c xmlwf/.libs/xmlwf /usr/local/bin/xmlwf ??????? conftools/install-sh -c -m 644 ./doc/xmlwf.1 /usr/local/man/man1 /home/earwax/soap/expat-1.95.8 # ? ? ? /home/earwax/soap/XML-Parser-2.34 # find / -name "libexpat.a" /usr/local/lib/libexpat.a ? ? /home/earwax/soap/XML-Parser-2.34 # find / -name "expat.h" /usr/local/include/expat.h /home/earwax/soap/XML-Parser-2.34 # perl Makefile.PL EXPATLIBPATH=/usr/local/lib EXPATINCPATH=/usr/local/include ? Writing Makefile for XML::Parser::Expat Writing Makefile for XML::Parser /home/earwax/soap/XML-Parser-2.34 # ? Make the perl file as follows: ??????Issue - must use cc instead of gcc so use make CC=gcc /home/earwax/soap/XML-Parser-2.34 # make CC=gcc ??????? gcc -c -I/usr/local/include -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384 -q32 -D_LARGE_FILES -qlonglong -O ???? -DVERSION=\"2.34\"? -DXS_VERSION=\"2.34\"? -I/usr/opt/perl5/lib/5.6.0/aix/CORE? Expat.c gcc: unrecognized option `-qmaxmem=16384' gcc: unrecognized option `-q32' gcc: unrecognized option `-qlonglong' In file included from Expat.xs:12: /usr/local/include/expat.h:18: expat_external.h: A file or directory in the path name does not exist. make: 1254-004 The error code from the last command is 1. ? ? Stop. make: 1254-004 The error code from the last command is 2. ? ? Stop. From karl at waclawek.net Tue Nov 29 22:02:08 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 16:02:08 -0500 Subject: [Expat-discuss] Install issues, lost expat_external.h In-Reply-To: References: Message-ID: <438CC1D0.5050804@waclawek.net> pappy at vappy.com wrote: > Hi I'm trying to install expat and then the PERL /XML-Parser-2.34 after that on my AIX 5.x system with root. It seems as though expat installs OK, but when I go to install the XML-Parser it says it can't find the expat_external.h file (see way on the bottom). Does anybody have any idea what is going on? When I search my system for expat_external.h, it only finds it in the expat install source directory (e.g. /home/earwax/soap/expat-1.95.8/lib/expat_external.h) I would have expected expat_external.h to have been installed on the system, maybe in /usr/local/include? > Has been reported multiple times, just search the bug tracker. On some systems the install utilities fail, but a workaround has been implemented in CVS. Karl From graham-expat at simulcra.org Tue Nov 29 23:19:31 2005 From: graham-expat at simulcra.org (Graham Bennett) Date: Tue, 29 Nov 2005 22:19:31 +0000 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <438C5F0E.2020402@waclawek.net> References: <438C5F0E.2020402@waclawek.net> Message-ID: <20051129221931.GA10675@lamity.org> On Tue, Nov 29, 2005 at 09:00:46AM -0500, Karl Waclawek wrote: > > We are trying to decide whether we should change some API return values > to 64 bit integers to support file sizes > 2GB. Affected would be these > API members: > > XML_GetCurrentByteIndex() > XML_GetCurrentByteCount() > XML_GetCurrentLineNumber() > XML_GetCurrentColumnNumber() > > Obviously this requires applications to be recompiled. > > The question is, how "breaking" would that change be? > How many applications are actually using these members? > > Should this be delayed after the release of Expat 2.0? When you say change to 64-bit, do you mean explicitly 64-bit on all platforms? I would have thought it better to use something like size_t, which would be of the appropriate size on each platform. Graham -- Graham Bennett From Paul_K_Fisher at bmc.com Tue Nov 29 23:57:27 2005 From: Paul_K_Fisher at bmc.com (Fisher, Paul_K (Houston)) Date: Tue, 29 Nov 2005 16:57:27 -0600 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? Message-ID: It is certainly possible to have >2G of XML processed on a 32-bit platform, even if the doc is processed from file (large file support exists in modern OS versions.) I think that change proposed by Karl is a good one. If you changed the declaration to the moral equivalent of uint64_t (C99) then people with old code would get an integer truncation warning when they recompile against the new version. For Windows if you change the default DLL name most people will not fall into running previously compiled code against the new version. All reasonable to do on a major version change. paul -----Original Message----- From: expat-discuss-bounces at libexpat.org on behalf of Graham Bennett Sent: Tue 11/29/2005 4:19 PM To: Karl Waclawek Cc: expat-discuss at libexpat.org Subject: Re: [Expat-discuss] 64 bit integers in Expat 2.0? On Tue, Nov 29, 2005 at 09:00:46AM -0500, Karl Waclawek wrote: > > We are trying to decide whether we should change some API return values > to 64 bit integers to support file sizes > 2GB. Affected would be these > API members: > > XML_GetCurrentByteIndex() > XML_GetCurrentByteCount() > XML_GetCurrentLineNumber() > XML_GetCurrentColumnNumber() > > Obviously this requires applications to be recompiled. > > The question is, how "breaking" would that change be? > How many applications are actually using these members? > > Should this be delayed after the release of Expat 2.0? When you say change to 64-bit, do you mean explicitly 64-bit on all platforms? I would have thought it better to use something like size_t, which would be of the appropriate size on each platform. Graham -- Graham Bennett _______________________________________________ Expat-discuss mailing list Expat-discuss at libexpat.org http://mail.libexpat.org/mailman/listinfo/expat-discuss From karl at waclawek.net Wed Nov 30 00:07:06 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 18:07:06 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <20051129221931.GA10675@lamity.org> References: <438C5F0E.2020402@waclawek.net> <20051129221931.GA10675@lamity.org> Message-ID: <438CDF1A.2000007@waclawek.net> Graham Bennett wrote: >On Tue, Nov 29, 2005 at 09:00:46AM -0500, Karl Waclawek wrote: > > >>We are trying to decide whether we should change some API return values >>to 64 bit integers to support file sizes > 2GB. Affected would be these >>API members: >> >> >When you say change to 64-bit, do you mean explicitly 64-bit on all >platforms? > > Yes. >I would have thought it better to use something like size_t, which would >be of the appropriate size on each platform. > > The point is that even on 32bit platforms, file sizes > 2GB are supported nowadays. size_t would therefore not be appropriate, as it would be 32bit on such a platform. Karl From karl at waclawek.net Wed Nov 30 00:19:31 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 18:19:31 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: References: Message-ID: <438CE203.9070206@waclawek.net> Fisher, Paul_K (Houston) wrote: >It is certainly possible to have >2G of XML processed on a 32-bit platform, even if the doc is processed from file (large file support exists in modern OS versions.) > >I think that change proposed by Karl is a good one. If you changed the declaration to the moral equivalent of uint64_t (C99) then people with old code would get an integer truncation warning when they recompile against the new version. For Windows if you change the default DLL name most people will not fall into running previously compiled code against the new version. All reasonable to do on a major version change. > > > Actually, Rolf Ade suggested this as a feature request. Now here are the issues: - Expat 2.0 is supposed to be just the final, stable release of the 1.95.x series. So introducing such a change that late might not seem appropriate. - On Windows, the library names have never had a version included. So, one solution could be to make it a compile time option, and have the default binary use the old compatible 32bit values. Later - post 2.0 - we could remove the compile option and make 64bit values the default. Karl From nickmacd at gmail.com Wed Nov 30 00:20:25 2005 From: nickmacd at gmail.com (Nick MacDonald) Date: Tue, 29 Nov 2005 18:20:25 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <438C5F0E.2020402@waclawek.net> References: <438C5F0E.2020402@waclawek.net> Message-ID: I'm guessing that people that need to support huge files (>2GB) generally know this. You could add some simple checking in the code. When the file is first opened, do a stat on it and see if its too huge, and large file support not enabled: #ifndef EXPAT_HUGE_FILE_SUPPORT if currentFileSize() >0xffffffff then { return warningOrErrorCode; } #endif Otherwise you just make a suitable type and hope that people writing new code are willing to adapt: #ifdef EXPAT_HUGE_FILE_SUPPORT typedef uint64 xmlFilePos_t; #else typedef unit32 xmlFilePos_t; #endif Nick On 11/29/05, Karl Waclawek wrote: > > > We are trying to decide whether we should change some API return values > to 64 bit integers to support file sizes > 2GB. Affected would be these > API members: > > XML_GetCurrentByteIndex() > XML_GetCurrentByteCount() > XML_GetCurrentLineNumber() > XML_GetCurrentColumnNumber() > > Obviously this requires applications to be recompiled. > > The question is, how "breaking" would that change be? > How many applications are actually using these members? > > Should this be delayed after the release of Expat 2.0? > > Karl > _______________________________________________ > Expat-discuss mailing list > Expat-discuss at libexpat.org > http://mail.libexpat.org/mailman/listinfo/expat-discuss > -- Nick MacDonald NickMacD at gmail.com From graham-expat at simulcra.org Wed Nov 30 00:25:20 2005 From: graham-expat at simulcra.org (Graham Bennett) Date: Tue, 29 Nov 2005 23:25:20 +0000 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <438CE203.9070206@waclawek.net> References: <438CE203.9070206@waclawek.net> Message-ID: <20051129232520.GB10675@lamity.org> On Tue, Nov 29, 2005 at 06:19:31PM -0500, Karl Waclawek wrote: > Fisher, Paul_K (Houston) wrote: > > >It is certainly possible to have >2G of XML processed on a 32-bit platform, even if the doc is processed from file (large file support exists in modern OS versions.) > > > >I think that change proposed by Karl is a good one. If you changed the declaration to the moral equivalent of uint64_t (C99) then people with old code would get an integer truncation warning when they recompile against the new version. For Windows if you change the default DLL name most people will not fall into running previously compiled code against the new version. All reasonable to do on a major version change. > > > > > > > Actually, Rolf Ade suggested this as a feature request. > > Now here are the issues: > - Expat 2.0 is supposed to be just the final, stable release of the > 1.95.x series. > So introducing such a change that late might not seem appropriate. > - On Windows, the library names have never had a version included. > So, one solution could be to make it a compile time option, and have > the default binary use the old compatible 32bit values. Later - post > 2.0 - we could > remove the compile option and make 64bit values the default. Perhaps just having a separate set of 'long' functions corresponding to each of the ones you listed but returning 64-bit types would be the easiest way to go. -- Graham Bennett From karl at waclawek.net Wed Nov 30 04:09:02 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 22:09:02 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: References: <438C5F0E.2020402@waclawek.net> Message-ID: <438D17CE.5090204@waclawek.net> Nick MacDonald wrote: >I'm guessing that people that need to support huge files (>2GB) generally >know this. You could add some simple checking in the code. > >When the file is first opened, do a stat on it and see if its too huge, and >large file support not enabled: > >#ifndef EXPAT_HUGE_FILE_SUPPORT >if currentFileSize() >0xffffffff then >{ > return warningOrErrorCode; >} >#endif > > There is just one problem: Expat doesn't know about files. > >Otherwise you just make a suitable type and hope that people writing new >code are willing to adapt: > >#ifdef EXPAT_HUGE_FILE_SUPPORT >typedef uint64 xmlFilePos_t; >#else >typedef unit32 xmlFilePos_t; >#endif > > New code doesn't concern me, backward's compatibility does. But an option to turn 64 bit values on/off might be reasonable. Karl From karl at waclawek.net Wed Nov 30 04:13:40 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue, 29 Nov 2005 22:13:40 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <20051129232520.GB10675@lamity.org> References: <438CE203.9070206@waclawek.net> <20051129232520.GB10675@lamity.org> Message-ID: <438D18E4.80508@waclawek.net> Graham Bennett wrote: >On Tue, Nov 29, 2005 at 06:19:31PM -0500, Karl Waclawek wrote: > > >>Fisher, Paul_K (Houston) wrote: >> >> >> >>>It is certainly possible to have >2G of XML processed on a 32-bit platform, even if the doc is processed from file (large file support exists in modern OS versions.) >>> >>>I think that change proposed by Karl is a good one. If you changed the declaration to the moral equivalent of uint64_t (C99) then people with old code would get an integer truncation warning when they recompile against the new version. For Windows if you change the default DLL name most people will not fall into running previously compiled code against the new version. All reasonable to do on a major version change. >>> >>> >>> >>> >>> >>Actually, Rolf Ade suggested this as a feature request. >> >>Now here are the issues: >>- Expat 2.0 is supposed to be just the final, stable release of the >>1.95.x series. >> So introducing such a change that late might not seem appropriate. >>- On Windows, the library names have never had a version included. >> So, one solution could be to make it a compile time option, and have >> the default binary use the old compatible 32bit values. Later - post >>2.0 - we could >> remove the compile option and make 64bit values the default. >> >> > >Perhaps just having a separate set of 'long' functions corresponding to >each of the ones you listed but returning 64-bit types would be the >easiest way to go. > > Yes, that might be an option as well. It just doesn't feel "right" for me to add four new alternative API members when the original ones aren't used that often. API bloat? Karl From nickmacd at gmail.com Wed Nov 30 15:30:30 2005 From: nickmacd at gmail.com (Nick MacDonald) Date: Wed, 30 Nov 2005 09:30:30 -0500 Subject: [Expat-discuss] 64 bit integers in Expat 2.0? In-Reply-To: <438D18E4.80508@waclawek.net> References: <438CE203.9070206@waclawek.net> <20051129232520.GB10675@lamity.org> <438D18E4.80508@waclawek.net> Message-ID: Well... not that the Windows API should stand as a stunning example of clarity, but I believe they have two entries for a lot of functions (I believe they nest, but not sure as I don't spend much time writing non-portable code for specific OSes)... one for Unicode and one for non-Unicode. Maybe you combine two ideas... have function names provide the return type and optionally only include one set of names or the other depending on some build flag. That way old code doesn't break, new code can use the new functions, and eventually you could mark the old function names as deprecated. Since the problem you face is technically only in one direction, you could remove the old function names in favour of new function names, and optionally include a macro to "rename" the new functions so they still appear present for old code. And maybe I'm just babbling... being that I have never used those particular API functions anyway... ;-) On 11/29/05, Karl Waclawek wrote: > > Yes, that might be an option as well. > It just doesn't feel "right" for me to add four new alternative API > members > when the original ones aren't used that often. API bloat? >