Menu
▾
▴
tclxml-users — Discussion on using the TclXML package
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(11) |
Feb
(2) |
Mar
(1) |
Apr
(4) |
May
(23) |
Jun
(17) |
Jul
(1) |
Aug
(17) |
Sep
(4) |
Oct
(14) |
Nov
(1) |
Dec
(2) |
| 2002 |
Jan
|
Feb
(2) |
Mar
(15) |
Apr
|
May
(19) |
Jun
(2) |
Jul
(8) |
Aug
(24) |
Sep
(21) |
Oct
(17) |
Nov
(11) |
Dec
(20) |
| 2003 |
Jan
(17) |
Feb
(19) |
Mar
(21) |
Apr
(13) |
May
(14) |
Jun
(7) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
| 2004 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(5) |
Jul
(12) |
Aug
(3) |
Sep
(14) |
Oct
(1) |
Nov
(4) |
Dec
(3) |
| 2005 |
Jan
(1) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2006 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2007 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
|
From: Steve B. <Ste...@zv...> - 2002-08-28 11:15:08
|
Derek Fountain wrote: > I have a parent node which has a whole bunch of children. Each child has a > number of sub-nodes, and can be quite large. I want to change the order of > the children under the parent node. That is, this: > > <parent> > <child>1</child> > <child>2</child> > <child>3</child> > </parent> > > might become this: > > <parent> > <child>2</child> > <child>1</child> > <child>3</child> > </parent> > > What's the most efficient way to do that? I'm using TclDOM and Use the 'insertBefore' method of the dom::node command. Ie. get the token of the child you want to move, the token of the node you want to move the node in front of, and the token of the parent. Then: dom::node insertBefore $parent $moving $inFrontOfMe This method automatically updates the tree to make the move happen. It works no matter where in the tree $moving was originally. HTHs, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Derek F. <fo...@hu...> - 2002-08-28 09:37:02
|
I have a parent node which has a whole bunch of children. Each child has a number of sub-nodes, and can be quite large. I want to change the order of the children under the parent node. That is, this: <parent> <child>1</child> <child>2</child> <child>3</child> </parent> might become this: <parent> <child>2</child> <child>1</child> <child>3</child> </parent> What's the most efficient way to do that? I'm using TclDOM and ActiveTcl-8.3.4.3 on both Linux and Windows. -- The past: Smart users in front of dumb terminals |
|
From: Steve B. <Ste...@zv...> - 2002-08-26 21:44:37
|
db...@hs... wrote: > I am using TclDOM to construct DOM tree for a document. Can someone > tell me how I can query the DOM tree based on attribute values of the nodes. Massive plug: This will be covered in the TclDOM tutorial at the upcoming Tcl Conference in Vancouver. So enrol in the tute, register for the conference and come to Vancouver! ==== selectNode accepts an XPath expression and returns a (static) list of nodes that match the expression. To learn about XPath, grab any good book on XSLT, such as Mike Kay's XSLT Programmer's Reference. With XPath, attributes may be selected using the attribute:: axis, or '@' for short. For example, //*/@href will select all attributes named 'href' in the document. HTHs, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: <db...@hs...> - 2002-08-26 13:15:25
|
Hi, I am using TclDOM to construct DOM tree for a document. Can someone tell me how I can query the DOM tree based on attribute values of the nodes. Best Regards, vijay DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. HSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. |
|
From: Steve B. <Ste...@zv...> - 2002-08-26 09:11:17
|
Dear Yogesh, You wrote: > I have some doubts regarding TclDOM parsing. > I am parsing using TclDom, i am able to parse but not satisfied with the > performance > when it comes to the speed. I am reading from one xml document and parsing > the other > xml document. This job when i did using VB and MSXML parser, it is quite > fast as compared > to using TclDOM. It is nearly 8 times slower. It took 45 seconds to parse > read three entried > from the first xml document and parse the other one. The Tcl implementation of TclDOM (and TclXML, the package that actually does the parsing) is naturally quite slow. MSXML is implemented in C++. There is now a version of TclDOM that uses libxml2. libxml2 is written in C and is *very* fast. By comparison, I ran some simple tests over the weekend and TclDOM/libxml2 is more than 20 times faster than TclDOM/tcl (and by inference is faster than MSXML). It would appear that you are using MS Windows. I'm cc'ing this message to the tclxml-users mailing list in case anyone has built TclDOM/libxml2 for Windows and might be willing to share it. Other alternatives are TclDOMPro (part of the TclDOM distribution) or tDOM (different API). Cheers, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Steve B. <Ste...@zv...> - 2002-08-25 22:55:08
|
Please use tcl...@li....
The Yahoo! group is now defunct.
vjaydodda wrote:
> I have to process some queries based on the DOM tree for the
> document. Can some body suggest some examples on how this can be done
> in TclDOM.
Use the 'selectNode' method of the dom::DOMImplementation
or dom::node command. The former is mainly for absolute
paths, the latter for relative paths.
I'll be giving a tutorial covering this at the upcoming
Tcl conference in Vancouver, so the best thing to do
would be to enrol in the TclDOM tute.
However, I am currently updating the Zveno course materials
for the course so examples will be online soon - probably
after the conference.
In the meantime, try something like:
dom::DOMImplementation selectNode $doc {/Example/value/text()}
HTHs,
Steve Ball
--
Steve Ball | XSLT Standard Library | Training & Seminars
Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas
http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development
Ste...@zv... +---------------------------+---------------------
Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099
|
|
From: Joe E. <jen...@fl...> - 2002-08-20 05:37:20
|
[Sorry for the late reply -- I just got back from vacation] On Thu, 15 Aug 2002, Larry W. Virden wrote: > Okay, I decided to just run the configure in tcldom-2.2/src and see what > happened. I got it to configure, the code built (with lots of warnings > about prototype problems - but I'm using Tcl 8.4 b2 so that doesn't > surprise me). > > Then I did a make test and got this as the summary: > > all.tcl: Total 326 Passed 159 Skipped 144 Failed 23 > Sourced 11 Test Files. > Files with failing tests: [...] > some of the failed tests include: > [...] > and so on - I can send all the errors if that seems useful. > > Anyone with an idea what might be going wrong? Executive summary: Steve enhanced the test suite, and Joe hasn't gotten around to updating tcldom/src to match it yet. If tcldom/src compiles, links, and installs without any hard errors, then you can (probably) safely ignore test suite failures. As Steve has mentioned, tcldom/src holds a separate code base, which is _supposed_ to be compatible with the main TclDOM distribution, but might not be due to different maintenance schedules. In this case, tcldom/src has not had any significant changes since the 2.0 release, so whatever worked before should continue to work now. (I don't yet know what's new in TclDOM 2.2, so new code written to take advantage of the 2.2 API might not work with the package provided by tcldom/src). --Joe English jen...@fl... |
|
From: Derek F. <fo...@hu...> - 2002-08-19 11:56:11
|
> TclDOM is all-Tcl, so it would be surprising to get a > segv. However, ActiveTcl includes TclExpat (the expat > wrapper for TclXML). I suspect that it is TclXML/expat > segv'ing while parsing the XML document. Someone on c.l.t reproduced it with a core, and the crash was indeed in that TclExpat thing. I compiled a Tcl-8.3.4.3 from scratch and it didn't fail there. > Try parsing using the Tcl parser, ie > > set doc [dom::parse $xml -parser tcl] Ah! That makes the problem go away, at least in a quick test I just ran. That's great - I was in an embarrassing hole for a while there. Thanks. -- The past: Smart users in front of dumb terminals |
|
From: Steve B. <Ste...@zv...> - 2002-08-19 02:12:11
|
Derek Fountain wrote: > I've got ActiveTcl-8.3.4.3 on a Linux box, and tried to run this script: [...snip...] > When I run the script, I get a segv back. There's no core. TclDOM is all-Tcl, so it would be surprising to get a segv. However, ActiveTcl includes TclExpat (the expat wrapper for TclXML). I suspect that it is TclXML/expat segv'ing while parsing the XML document. Try parsing using the Tcl parser, ie set doc [dom::parse $xml -parser tcl] Just a couple of days ago I managed to compile TclXML/expat on my MacOSX m/c and core dumps are occurring in the markup declaration code (exactly what was described in the c.l.t. postings). Investigations are underway, but getting the Tcl2K2 paper written takes higher priority ;-) Cheers, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Larry W. V. <lv...@ca...> - 2002-08-16 18:07:38
|
As a followup to my continued reports of attempting to successfully build and install the tcldom tcl extension, following the most recent msgs from list members, I was able to locate a version of libxml2 (version 2.4.23) ... I was not able to locate a tar file with the name "devel" in it, so I don't know if I am missing something or not. Anyways, I configured, built and installed that library. I returned to tcldom 2.2 and configured thusly: /vol/tclsrcsol/tcl84/tcldom/configure --prefix=/usr/tcl84 --enable-symbols --enable-shared --enable-xml2 --with-xml2=/projects/intranet/lib and that created a Makefile. I then typed make all and after a while, got this error: cc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DVERSION=\"2.2\" -DUSE_TCL_STUBS=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_DIRENT64=1 -DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1 -DWORDS_BIGENDIAN=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TZNAME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_BLKSIZE=1 -Dstrtod=fixstrtod -DSTDC_HEADERS=1 -Dsocklen_t=unsigned -DNO_UNION_WAIT=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -D_REENTRANT=1 -D_POSIX_PTHREAD_SEMANTICS=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -I/usr/local/include/libxml2 -g -KPIC -I/vol/tclsrcsol/tcl84/tcldom -c `echo /vol/tclsrcsol/tcl84/tcldom/src-libxml2/tcldom-libxml2.c` -o tcl! dom-libxml2.o "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 23: cannot find include file: <tcl.h> "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 80: syntax error before or at: Tcl_Obj "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 80: cannot recover from previous errors cc: acomp failed for /vol/tclsrcsol/tcl84/tcldom/src-libxml2/tcldom-libxml2.c make[1]: *** [tcldom-libxml2.o] Error 2 make[1]: Leaving directory `/vol/tclsrcsol/tcl84/tcldom/src-libxml2' make: *** [libtcldom-libxml2-2.2.so] Error 2 Note that the -I flag for libxml2 is wrong, and the -I flag for Tcl is missing altogether. If I edit the src-libxml2/Makefile so that it uses $(INCLUDES) instead of $(TCL_INCLUDES) - which apparently isn't defined anywhere and I edit in the directory for the xml2 include directory rather than the hard coded /usr/local/include prefix, I appear to get a compiled .so for tcldom's library. -- Tcl'2002 Sept 16, 2002, Vancouver, BC http://www.tcl.tk/community/tcl2002/ Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
|
From: Steve B. <Ste...@zv...> - 2002-08-16 03:01:20
|
Larry W. Virden wrote:
> Okay, I decided to just run the configure in tcldom-2.2/src and see what
> happened.
That's Joe English's code, so I can't really comment much on it.
> I got it to configure, the code built (with lots of warnings
> about prototype problems - but I'm using Tcl 8.4 b2 so that doesn't
> surprise me).
>
> Then I did a make test and got this as the summary:
Before releasing 2.2 I went through the test suite and updated
to tcltest 2.1. I allocated constraints, dom_tcl, dom_c and
dom_libxml2, to many of the tests to account for differences
in the subpackages capabilities and inconsistencies.
This work is not yet complete; the fact that only 23 failed
is pretty good ;-)
In order to get the tests functioning properly, you must
enable one of the constraints. Start a tclsh and load the
DOM implementation you wish to test, eg. 'package require dom::c'.
Then 'source all.tcl' and ignore the results.
Then type 'testConstraint dom_c 1' and run 'source all.tcl'
again and you will get a true error count. You can do a
similar thing to test the all-Tcl implementation.
I have yet to set this up in a convenient script
(but like I said before, "It works for me").
If you look closely at the failures, you'll notice that with
some of them the difference is in different serialization
of the DOM tree into XML. In fact, these are not really
failures since the XML is equivalent. However, Tcl is
testing with character-by-character exactness.
For example:
<?xml version='1.0'?>
<Test some="attribute"/>
is *exactly* the same document as
<?xml version="1.0"?>
<Test some='attribute'/>
even though syntactically they are different. Technically
speaking, TclDOM works at the XML Infoset level, rather than
the raw XML syntax level.
Also, I've already committed fixes for a couple of those errors.
Cheers,
Steve Ball
> all.tcl: Total 326 Passed 159 Skipped 144 Failed 23
> Sourced 11 Test Files.
> Files with failing tests: DOMImplementation.test element.test node.test parse.te
> st serialization.test xmlswitch.test zzlast.test
> Number of tests skipped for each constraint:
> 114 dom_c
> 1 dom_libxml2
> 13 dom_tcl
> 1 dom_tcl || dom_libxml2
> 2 dom_tcl || tcl_libxml2
> 2 emptyTest
> 3 knownBug
> 8 as
>
> some of the failed tests include:
> /usr/ccs/bin/ld -G -z text -o tcldom2.0g.so -R /usr/tcl84/lib \
> tcldompro.o tdpExpat.o traversal.o livelist.o -L/usr/tcl84/lib -lexpat0.
> 2 -L/usr/tcl84/lib -ltclstub8.4g -L/usr/tcl84/lib -ltclstub8.4g
> TCLLIBPATH=`pwd` ; export TCLLIBPATH ; \
> (cd ../tests ; \
> /usr/tcl84/bin/tclsh8.4 all.tcl -verbose b) 2>&1 | tee test.log
> DOMImplementation.test
> Loaded dom version 2.2 via {
> if {[catch {package require dom::generic 2.2}]} {
> package require dom::tclgeneric
> } else {
> catch {package require dom::c}
> catch {package require dom::libxml2 2.2}
> }
> package provide dom 2.2
>
> # Both the C and pure Tcl versions of the generic layer
> # make use of the Tcl implementation.
>
> package require dom::tcl
> }
>
> ==== DOMImplementation-3.5 destroy an element node FAILED
> ==== Contents of test case:
>
> set doc [dom::DOMImplementation create]
> set root [dom::document createElement $doc top]
> set node1 [dom::document createElement $root node]
> set node2 [dom::document createElement $root node]
> dom::node removeChild $root $node1
> dom::DOMImplementation destroy $node1
>
> dom::DOMImplementation serialize $doc
> ---- Result was:
> <?xml version='1.0'?>
> <!DOCTYPE top>
> <top><node/></top>
> ---- Result should have been (exact matching):
> <?xml version="1.0"?>
> <!DOCTYPE top>
> <top><node/></top>
>
> ==== DOMImplementation-3.5 FAILED
>
> error "no element found" at line 1 character 0
> while executing
> "$parser parse [lindex $args 0]"
> doctype.test
> document.test
> element.test
> ==== element-4.1 getAttribute FAILED
> ==== Contents of test case:
>
> dom::element getAttribute $e1 class
>
> ---- Result was:
>
> ---- Result should have been (exact matching):
> success
> ==== element-4.1 FAILED
> node.test
>
> ==== node-4.1 cget -childNodes FAILED
> ==== Contents of test case:
>
> set [::dom::node cget $doc -childNodes]
>
> ---- Result was:
> ::dom::tcl::document10(node3) ::dom::tcl::document10(node2)
> ---- Result should have been (exact matching):
> ::dom::tcl::document10(node2)
> ==== node-4.1 FAILED
>
> ==== node-4.4 cget -childNodes textNode FAILED
> ==== Contents of test case:
>
> set [::dom::node cget $child2 -childNodes]
>
> ---- Result was:
> can't read "": no such variable
> ---- Result should have been (exact matching):
>
> ---- Test completed normally; Return code was: 0
> ---- Return code should have been one of: 0 2
> ==== node-4.4 FAILED
>
> ==== node-4.5 configure -childNodes FAILED
> ==== Contents of test case:
>
> set [::dom::node configure $doc -childNodes]
>
> ---- Result was:
> ::dom::tcl::document10(node3) ::dom::tcl::document10(node2)
> ---- Result should have been (exact matching):
> ::dom::tcl::document10(node2)
> ==== node-4.5 FAILED
>
> ==== node-4.8 cget -childNodes textNode FAILED
> ==== Contents of test case:
>
> set [::dom::node configure $child2 -childNodes]
>
> ---- Result was:
> can't read "": no such variable
> ---- Result should have been (exact matching):
>
> ---- Test completed normally; Return code was: 0
> ---- Return code should have been one of: 0 2
>
> and so on - I can send all the errors if that seems useful.
>
> Anyone with an idea what might be going wrong?
--
Steve Ball | XSLT Standard Library | Training & Seminars
Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas
http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development
Ste...@zv... +---------------------------+---------------------
Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099
|
|
From: Steve B. <Ste...@zv...> - 2002-08-16 00:39:53
|
Andreas Kupries wrote: > Here are my experiences after having read the message below. > > 1. Got head of Tcl 8.3.4 branch > 1.a Compiled and installed in playground/sandbox > 2. Got head of tclxml/tcldom > 2.a Ran autoconf > 2.b. Configured with same prefix as tcl, did --enable-xml2 > configure did not find xml2 > > There is nothing in the docs telling us > where we can get libxml2. Stop. README now fixed. > Nit: make distclean leaves two directories behind, library and src-libxml2 > (in the build directory). Can be explained because srcdir contains these > two directories too, often builddir = srcdir. > > I tried a second configure of tcldom, with --disable-xml2. > No errors for that. > > Compilation fails nevertheless because the makefile tried to compile the > sources in src-libxml2 despite the fact that I just told it that libxml2 > is not available. > > That is not acceptable. A configure option which does nothing at all. The autoconf/configure scripts need some work. I'm looking for a volunteer for that. >>2. The sf.net tar file didn't include top level configure - >>is configure supposed to be done elsewhere? The README isn't clear. > > IMHO the source distribution has to have a 'configure'. For a checkout from > the CVS the situation is more fuzzy. I'll make sure the distribution includes a configure in future. >>3. After I ran autoconf to create the configure, configure >>reports this error: >>configure: error: cannot run /bin/ksh config/config.sub > > Not here. Thank heavens something worked! > Speculation: It seems as if the script install still does rely on the > information provided by the configure script. Peter Farmer wrote that part of the install script; he's probably the best one to answer that. >>I'm still uncertain about the purpose of the src and src-xml2 directories; >>the README doesn't mention either. > > The src directory contains the generic tcldom sources. The framework where > parsers etc can plug themselves into. Not quite. The src directory contains the sources for the TclDOMPro implementation (not yet integrated into the package build system - that's Joe English's code). The generic layer sources are tcldom.c and tcldom.h in the top directory. > src-libxml2 contains the glue code wrapping around libxml2 and making it > useable by the tcldom framework in src. Essentially a separate package. Correct. Cheers, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Steve B. <Ste...@zv...> - 2002-08-16 00:27:26
|
Larry W. Virden wrote: > 1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 - > anyone know why? You would have to ask ActiveState. I imagien they need a little time to integrate it. > 2. The sf.net tar file didn't include top level configure - > is configure supposed to be done elsewhere? The README isn't clear. Oops. I'll make sure the next release includes configure. > 3. After I ran autoconf to create the configure, configure reports this error: > configure: error: cannot run /bin/ksh config/config.sub > 4. after supplying that file, configure reports this error: > checking build system type... /bin/ksh: config/config.guess: not found > configure: error: cannot guess build type; you must specify one > 5. after supplying that file, configure reports this error: > checking for xml2 library file... configure: WARNING: Can't find xml2 library What can I say? I use ProjectBuilder under MacOSX to compile all of this stuff. It works for me ;-) If someone would like to contribute fixes to the autoconf files then I will gladly accept them. > README doesn't indicate where to find this library. The website lists the dependencies. I have updated the README with the libxml2 URL. > At this point, I gave up on that approach and tried the generic script install. > > 6. My attempt to run wish install.tcl generates this error: > Error in startup script: extra characters after close-brace > while executing > "proc Slave_Component {slave type args" > (file "./install.tcl" line 306) Sigh. I thought that was fixed some time ago. Now fixed. > 7. After removing DOS ^M (thinking that was the problem), I continue > to get this error. There is a syntax error in install.tcl > (I reported this earlier, along with a fix - what happened to that bug fix?) > > proc Slave_Component {slave type args}} { > should be > proc Slave_Component {slave type args} { See above. > 8. After fixing error, running install.tcl generates this error: > Build data file is missing. > Attempting to build from /vol/tclsrcsol/tcl84/tcldom-2.2/config.status > plus a tk dialog that says: > build status file Error > Warning: An error occured while parsing the build config status data. > No macros found Hmmm. Someone will need to investigate that further... Pete? > I have no idea whether that is significant or not - if not, perhaps the > errors should not be generated. If so, then perhaps the README could > be updated to let someone know what to do about it? > 9. After clicking on the okay button, the process continues and this error > appears: > Don't do "package require tcllib", ask for individual modules. > (Again, this is an error I submitted a fix for during the previous release!) That must be a leftover from TclXML - TclDOM doesn't use any tcllib modules itself. I have removed that line from install.data. > 10. The tcldom installer appears, with this in its status window: > No files matching pattern "./docs/*.html" were found > Again - if this is not significant, perhaps it should not be displayed. > If it is significant, then something should be said about what to do about it. That's not significant, but I will make sure that the nroff and HTML versions of the man page are in the next release. > 11. After cancelling that status window, the rest of the install proceeded. > > I'm still uncertain about the purpose of the src and src-xml2 directories; > the README doesn't mention either. I've added a MANIFEST file. I'm working on a v2.3 release to fix these problems, but have to get the Tcl2K2 paper written first ;-) Cheers, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Andreas K. <and...@Ac...> - 2002-08-15 22:23:40
|
> ------- Forwarded Message > > From: "Larry W. Virden" <lv...@ca...> > Subject: [Tclxml-users] Report of my attempt to install tcldom 2.2 > Sender: tcl...@li... > To: tcl...@li... > Message-id: <200...@ca...> Here are my experiences after having read the message below. 1. Got head of Tcl 8.3.4 branch 1.a Compiled and installed in playground/sandbox 2. Got head of tclxml/tcldom 2.a Ran autoconf 2.b. Configured with same prefix as tcl, did --enable-xml2 configure did not find xml2 There is nothing in the docs telling us where we can get libxml2. Stop. Nit: make distclean leaves two directories behind, library and src-libxml2 (in the build directory). Can be explained because srcdir contains these two directories too, often builddir = srcdir. I tried a second configure of tcldom, with --disable-xml2. No errors for that. Compilation fails nevertheless because the makefile tried to compile the sources in src-libxml2 despite the fact that I just told it that libxml2 is not available. That is not acceptable. A configure option which does nothing at all. More comments below. > 1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 - > anyone know why? No. At least the changelog in the latest snapshot (Aug 12) looks as if it is a part of tcldom 2.2. > 2. The sf.net tar file didn't include top level configure - > is configure supposed to be done elsewhere? The README isn't clear. IMHO the source distribution has to have a 'configure'. For a checkout from the CVS the situation is more fuzzy. > 3. After I ran autoconf to create the configure, configure > reports this error: > configure: error: cannot run /bin/ksh config/config.sub Not here. > 4. after supplying that file, configure reports this error: > checking build system type... /bin/ksh: config/config.guess: not found > configure: error: cannot guess build type; you must specify one Not here. > 5. after supplying that file, configure reports this error: > checking for xml2 library file... configure: WARNING: Can't find > xml2 library > README doesn't indicate where to find this library. Yep, exactly what I encountered too. > At this point, I gave up on that approach and tried the generic > script install. > > 6. My attempt to run wish install.tcl generates this error: > Error in startup script: extra characters after close-brace > while executing > "proc Slave_Component {slave type args" > (file "./install.tcl" line 306) > 7. After removing DOS ^M (thinking that was the problem), I continue > to get this error. There is a syntax error in install.tcl > (I reported this earlier, along with a fix - what happened to > that bug fix?) > > proc Slave_Component {slave type args}} { > should be > proc Slave_Component {slave type args} { > > 8. After fixing error, running install.tcl generates this error: > Build data file is missing. > Attempting to build from /vol/tclsrcsol/tcl84/tcldom-2.2/config.status > plus a tk dialog that says: > build status file Error > Warning: An error occured while parsing the build config status data. > No macros found Speculation: It seems as if the script install still does rely on the information provided by the configure script. > > I have no idea whether that is significant or not - if not, perhaps the > errors should not be generated. If so, then perhaps the README could > be updated to let someone know what to do about it? > > 9. After clicking on the okay button, the process continues and this error > appears: > Don't do "package require tcllib", ask for individual modules. > (Again, this is an error I submitted a fix for during the > previous release!) > > > 10. The tcldom installer appears, with this in its status window: > No files matching pattern "./docs/*.html" were found > Again - if this is not significant, perhaps it should not be displayed. > If it is significant, then something should be said about what to > do about it. > > 11. After cancelling that status window, the rest of the install > proceeded. > > I'm still uncertain about the purpose of the src and src-xml2 directories; > the README doesn't mention either. The src directory contains the generic tcldom sources. The framework where parsers etc can plug themselves into. src-libxml2 contains the glue code wrapping around libxml2 and making it useable by the tcldom framework in src. Essentially a separate package. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Join Tcl'2002 in Vancouver http://www.tcl.tk/community/tcl2002/ ** Registration is open ** |
|
From: Larry W. V. <lv...@ca...> - 2002-08-15 13:33:46
|
Okay, I decided to just run the configure in tcldom-2.2/src and see what
happened. I got it to configure, the code built (with lots of warnings
about prototype problems - but I'm using Tcl 8.4 b2 so that doesn't
surprise me).
Then I did a make test and got this as the summary:
all.tcl: Total 326 Passed 159 Skipped 144 Failed 23
Sourced 11 Test Files.
Files with failing tests: DOMImplementation.test element.test node.test parse.te
st serialization.test xmlswitch.test zzlast.test
Number of tests skipped for each constraint:
114 dom_c
1 dom_libxml2
13 dom_tcl
1 dom_tcl || dom_libxml2
2 dom_tcl || tcl_libxml2
2 emptyTest
3 knownBug
8 as
some of the failed tests include:
/usr/ccs/bin/ld -G -z text -o tcldom2.0g.so -R /usr/tcl84/lib \
tcldompro.o tdpExpat.o traversal.o livelist.o -L/usr/tcl84/lib -lexpat0.
2 -L/usr/tcl84/lib -ltclstub8.4g -L/usr/tcl84/lib -ltclstub8.4g
TCLLIBPATH=`pwd` ; export TCLLIBPATH ; \
(cd ../tests ; \
/usr/tcl84/bin/tclsh8.4 all.tcl -verbose b) 2>&1 | tee test.log
DOMImplementation.test
Loaded dom version 2.2 via {
if {[catch {package require dom::generic 2.2}]} {
package require dom::tclgeneric
} else {
catch {package require dom::c}
catch {package require dom::libxml2 2.2}
}
package provide dom 2.2
# Both the C and pure Tcl versions of the generic layer
# make use of the Tcl implementation.
package require dom::tcl
}
==== DOMImplementation-3.5 destroy an element node FAILED
==== Contents of test case:
set doc [dom::DOMImplementation create]
set root [dom::document createElement $doc top]
set node1 [dom::document createElement $root node]
set node2 [dom::document createElement $root node]
dom::node removeChild $root $node1
dom::DOMImplementation destroy $node1
dom::DOMImplementation serialize $doc
---- Result was:
<?xml version='1.0'?>
<!DOCTYPE top>
<top><node/></top>
---- Result should have been (exact matching):
<?xml version="1.0"?>
<!DOCTYPE top>
<top><node/></top>
==== DOMImplementation-3.5 FAILED
error "no element found" at line 1 character 0
while executing
"$parser parse [lindex $args 0]"
doctype.test
document.test
element.test
==== element-4.1 getAttribute FAILED
==== Contents of test case:
dom::element getAttribute $e1 class
---- Result was:
---- Result should have been (exact matching):
success
==== element-4.1 FAILED
node.test
==== node-4.1 cget -childNodes FAILED
==== Contents of test case:
set [::dom::node cget $doc -childNodes]
---- Result was:
::dom::tcl::document10(node3) ::dom::tcl::document10(node2)
---- Result should have been (exact matching):
::dom::tcl::document10(node2)
==== node-4.1 FAILED
==== node-4.4 cget -childNodes textNode FAILED
==== Contents of test case:
set [::dom::node cget $child2 -childNodes]
---- Result was:
can't read "": no such variable
---- Result should have been (exact matching):
---- Test completed normally; Return code was: 0
---- Return code should have been one of: 0 2
==== node-4.4 FAILED
==== node-4.5 configure -childNodes FAILED
==== Contents of test case:
set [::dom::node configure $doc -childNodes]
---- Result was:
::dom::tcl::document10(node3) ::dom::tcl::document10(node2)
---- Result should have been (exact matching):
::dom::tcl::document10(node2)
==== node-4.5 FAILED
==== node-4.8 cget -childNodes textNode FAILED
==== Contents of test case:
set [::dom::node configure $child2 -childNodes]
---- Result was:
can't read "": no such variable
---- Result should have been (exact matching):
---- Test completed normally; Return code was: 0
---- Return code should have been one of: 0 2
and so on - I can send all the errors if that seems useful.
Anyone with an idea what might be going wrong?
--
Tcl'2002 Sept 16, 2002, Vancouver, BC http://www.tcl.tk/community/tcl2002/
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
|
|
From: Larry W. V. <lv...@ca...> - 2002-08-15 13:07:40
|
1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 - anyone know why? 2. The sf.net tar file didn't include top level configure - is configure supposed to be done elsewhere? The README isn't clear. 3. After I ran autoconf to create the configure, configure reports this error: configure: error: cannot run /bin/ksh config/config.sub 4. after supplying that file, configure reports this error: checking build system type... /bin/ksh: config/config.guess: not found configure: error: cannot guess build type; you must specify one 5. after supplying that file, configure reports this error: checking for xml2 library file... configure: WARNING: Can't find xml2 library README doesn't indicate where to find this library. At this point, I gave up on that approach and tried the generic script install. 6. My attempt to run wish install.tcl generates this error: Error in startup script: extra characters after close-brace while executing "proc Slave_Component {slave type args" (file "./install.tcl" line 306) 7. After removing DOS ^M (thinking that was the problem), I continue to get this error. There is a syntax error in install.tcl (I reported this earlier, along with a fix - what happened to that bug fix?) proc Slave_Component {slave type args}} { should be proc Slave_Component {slave type args} { 8. After fixing error, running install.tcl generates this error: Build data file is missing. Attempting to build from /vol/tclsrcsol/tcl84/tcldom-2.2/config.status plus a tk dialog that says: build status file Error Warning: An error occured while parsing the build config status data. No macros found I have no idea whether that is significant or not - if not, perhaps the errors should not be generated. If so, then perhaps the README could be updated to let someone know what to do about it? 9. After clicking on the okay button, the process continues and this error appears: Don't do "package require tcllib", ask for individual modules. (Again, this is an error I submitted a fix for during the previous release!) 10. The tcldom installer appears, with this in its status window: No files matching pattern "./docs/*.html" were found Again - if this is not significant, perhaps it should not be displayed. If it is significant, then something should be said about what to do about it. 11. After cancelling that status window, the rest of the install proceeded. I'm still uncertain about the purpose of the src and src-xml2 directories; the README doesn't mention either. -- Tcl'2002 Sept 16, 2002, Vancouver, BC http://www.tcl.tk/community/tcl2002/ Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
|
From: Derek F. <fo...@hu...> - 2002-08-14 14:31:53
|
I've got ActiveTcl-8.3.4.3 on a Linux box, and tried to run this script: --- #!/bin/sh # \ exec tclsh8.3 "$0" "$@" package require xml package require dom 2.2 package require Tclx set xml [read_file "wrapper.xml" 1024] set docNode [dom::DOMImplementation parse $xml] puts [dom::node cget $docNode -nodeType] --- (I've upgraded my TclDOM to 2.2, but 2.0 did this too.) My XML file "wrapper.xml" looks like this: --- <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE wrapper [ <!ELEMENT wrapper (wrappedbit+)> <!ELEMENT wrappedbit (#PCDATA)> <!ENTITY bit SYSTEM "wrappedbit.xml"> ]> <wrapper> &bit; </wrapper> --- and the "wrappedbit.xml" contains: --- <wrappedbit>Hello world</wrappedbit> --- When I run the script, I get a segv back. There's no core. Can anyone with a bit more knowledge confirm and/or tell what the problem is? -- The past: Smart users in front of dumb terminals |
|
From: Derek F. <fo...@hu...> - 2002-08-14 14:24:12
|
Hi,
I thought I'd have a look at the Tcl-only implementation of TclDOM-2.2. I
followed the readme and got this error from the installation script:
>wish install.tcl
Error in startup script: extra characters after close-brace
while executing
"proc Slave_Component {slave type args"
(file "install.tcl" line 306)
I went and had a look at that bit of code and found:
proc Slave_Component {slave type args}} {
which doesn't look at all right... ;o)
Removing the extra } made the script work.
--
The past: Smart users in front of dumb terminals
|
|
From: Steve B. <Ste...@zv...> - 2002-08-13 20:47:08
|
Cameron Laird wrote: > Here's a node: > <ns:some_element name = "myname" ...> > When I > dom::node cget $node -nodeName > I receive some_element. To determine ns, I have to > array set node [set $node] > puts "The namespace is $node(node_prefix)." > True? Is there a better way? Should this be obvious from > the documentation? DOM Level 2 provides the 'namespaceURI' and 'prefix' attributes on the Node interface for this purpose. In terms of TclDOM v2.2, you can use: dom::node cget $node -prefix to get the NS prefix (usually not of great interest) or dom::node cget $node -namespaceURI to the namespace URI (usually want you need to know). Looks like the TclDOM man page is not up-to-date wrt Level 2 features (sigh...). Please submit a documentation bug on SF. HTHs, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: Cameron L. <cl...@st...> - 2002-08-13 00:54:39
|
Here's a node: <ns:some_element name = "myname" ...> When I dom::node cget $node -nodeName I receive some_element. To determine ns, I have to array set node [set $node] puts "The namespace is $node(node_prefix)." True? Is there a better way? Should this be obvious from the documentation? |
|
From: Steve B. <Ste...@zv...> - 2002-08-09 10:57:57
|
Apologies for the spam that slipped through. I have changed the mailing list configuration to hopefully prevent any more being sent to the list. Cheers, Steve Ball -- Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |
|
From: <hel...@em...> - 2002-08-08 20:34:02
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0025)http://www.mealstogo.com/ --> <!-- saved from url=(0022)http://internet.e-mail --><HTML><HEAD><TITLE>Mealstogo : Bay Area's restaurant menus and restaurant delivery services. Food delivery in Bay Area, catering in Bay Area, food catering, Bay Area restaurant menus, restaurant food, restaurant delivery services, restaurant take out, togo restaurant delivery, togo food delivery, togo delivery service, togo restaurant menus, togo take out,togo Bay Area, togo catering, Bay Area catering, catering menus, restaurant catering, catering delivery service, office food delivery, office catering, business catering, business food delivery, office lunch, Bay Area's restaurant delivery services!</TITLE> <META content="text/html; charset=windows-1252" http-equiv=Content-Type> <META content="Updated restaurant menus for Dine-in, Pick-up and Delivery. To Go! is a unique delivery service that picks up meals from Bay Area's best restaurants and delivers them to your home or office in about an hour." name=description> <META content="Bay Area's restaurant menus and restaurant food delivery services. Food delivery in Bay Area, catering in Bay Area, food catering, Bay Area restaurant menus, restaurant food, restaurant delivery services, restaurant take out, togo restaurant delivery, togo food delivery, togo delivery service, togo restaurant menus, togo take out,togo Bay Area, togo catering, Bay Area catering, catering menus, restaurant catering, catering delivery service, office food delivery, office catering, business catering, business food delivery, office lunch, Bay Area's restaurant delivery services." name=keywords> <META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD> <BODY bgColor=#ffffff> <P> <TABLE border=0 width="100%"> <TBODY> <TR> <TD width="100%"> <P> <CENTER><IMG align=top height=100 src="http://www.mealstogo.com/logo500.gif" width=480><BR><FONT color=#00af00 face="Arial, Helvetica, sans-serif"></FONT><FONT color=#000000 size=+1>SAN FRANCISCO : 1-800-853-0211 PENINSULA : (650) 692-4200 <BR>Fax (650) 692-4882<BR><FONT face="Arial, Helvetica, sans-serif" size=-1></FONT>Delivery Charge: $8.00 Minimum Order: $15.00 Suggested Gratuity: 12%<BR>Hours:M-F 9:30-2:00PM 4:30-9:00PM , SAT & SUN's:4:30-9:00 PM</FONT><FONT size=-1><BR><FONT color=#ff0000 face="Arial, Helvetica, sans-serif" size=2><B>Please Select Your City for Restaurant Choices and Menus. <BR></B></FONT><B><FONT color=#008b00 face="Arial, Helvetica, sans-serif"></FONT></B><FONT color=#00af00 size=+1></FONT><FONT color=#00af00><A href="http://www.mealstogo.com/_SF.html"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[SAN FRANCISCO] </font></a><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_mil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1><BR></font></A><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_ssf.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[South SF & Brisbane] </font></A><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_mil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Millbrae]</FONT></A> <A href="http://www.mealstogo.com/_bur.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Burlingame]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_hil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Hillsborough]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sm.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[San Mateo]</font></A><FONT color=#00af00 size=+1><BR><A href="http://www.mealstogo.com/_fc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Foster City]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_bel.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Belmont]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[San Carlos]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_rs.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Redwoodshores]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_rc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Redwood City]</font></A><FONT color=#00af00 size=+1><BR><A href="http://www.mealstogo.com/_ath.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Atherton]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_mp.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Menlo Park]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_pa.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Palo Alto]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_la.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Los Altos]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_mv.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Mt. View]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sv.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Sunnyvale]</font></A> </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></CENTER><FONT size=-1><FONT color=#00af00><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1> <CENTER> <FONT color=#ffffff size=1><IMG align=bottom height=125 src="http://www.mealstogo.com/burger1.jpg" vspace=3 width=130></FONT><FONT color=#ffffff size=1>|</FONT><FONT color=#00af00 size=+1><IMG align=bottom src="http://www.mealstogo.com/ctogo.gif" vspace=6></FONT><FONT color=#ffffff size=1>|</FONT><FONT color=#00af00 size=+1><IMG align=bottom height=125 src="http://www.mealstogo.com/soup1.jpg" vspace=3 width=130><BR> <FONT color=#ff0000 face="Arial, Helvetica, sans-serif" size=2><B>YOUR RESTAURANT DELIVERY SERVICE<BR>Delivers from over 125 Bay Area restaurants. Established since 1992</B></FONT><BR></FONT><B><FONT color=#00af00><A href="mailto:Da...@me..." target=""><FONT face="Arial, Helvetica, sans-serif" size=2>Feedbacks, Comments and Suggestions</FONT></A></FONT></B> </CENTER> <CENTER><a><FONT color=#00af00 size=+1><IMG align=absMiddle border=0 height=20 hspace=6 src="http://counter.digits.com/wc/-rz/-d/6/kwsta" vspace=2 width=90></FONT> </a> </CENTER></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT><A><FONT size=-1><FONT color=#00af00><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></a></TD></TR></TBODY></TABLE><p> </p> <p><br> <font size="2">To be optout from our future mailing please email op...@em... </font></P> <p><font size="2">You can also opt out by mail; Please send your request to: </font></p> <p><font size="2">11314 Ventura Blvd Suite #141 <br> Studio City, CA 91604</font></p> <p><font size="2">Or by Phone (213) 216 8305</font></p> </BODY></HTML> |
|
From: Mats B. <ma...@pr...> - 2002-08-08 16:27:16
|
Hi all, I've found a really nasty bug in the xml-tcl parser when doing event based parsing together with the '-final 0' option. This typically happens when having a proc registered with fileevent on sockets that just feeds the parser, and when any element callback calls 'update' it triggers the event queue which feeds the parser with xml, which therefore comes in the wrong order. Hope you get it... It's a kind of reentrance problem. This problem is isolated in the script below. The output from a simple example is shown below, with and without the 'update' call. I have a proposed fix for this by embedding the parsing in another proc which is reentry safe. I think that this should go into the tcl-xml parser, either as a separate method, or the default 'parse' method. Opinion??? Best Wishes, Mats PS: You need my patched TclXML from "http://hem.fyristorg.com/matben/download/TclXML.tar.gz" Glad to see that my fixes for '-final 0' and error callbacks work :-) # OUTPUT ---------------------------------------------------- set data1 {<stream><base>Some text here</base><junk chop='off' } set data2 {type='public'/><cut>more stuff</cut></stream>} after idle [list $p parse $data2] $p parse $data1 ==> (Start) 'stream': ==> (Start) 'base': ==> (Data 'update') 'Some text here' <-- the idle handler is called here ==> (Start) 'junk': type public chop off ==> (End) 'junk' ==> (Start) 'cut': ==> (Data 'update') 'more stuff' ==> (End) 'cut' ==> (Error) errcode=illegalendtag, errmsg=end tag "stream" does not match open element "base" around line 0 ==> (End) 'base' Correct: ==> (Start) 'stream': ==> (Start) 'base': ==> (Data) 'Some text here' ==> (End) 'base' ==> (Start) 'junk': type public chop off ==> (End) 'junk' ==> (Start) 'cut': ==> (Data) 'more stuff' ==> (End) 'cut' ==> (End) 'stream' I think we quit here I think we quit here while executing "HandleError illegalendtag {end tag "stream" does not match open element "base" around line 0}" ("uplevel" body line 1) invoked from within "uplevel #0 $options(-errorcommand) [list illegalendtag "end tag \"$tag\" does not match open element \"[lindex $state(stack) end]\" around line $state..." (procedure "ParseEvent:ElementClose" line 9) invoked from within #- EXAMPLE SCRIPT -------------------------------------- package require xml set _wspc {[ \t\n\r]*} proc HandleStart {name attlist args} { puts "==> (Start) '$name': $attlist" } proc HandleEnd {name args} { global myParser puts "==> (End) '$name'" } proc HandleText {data} { global _wspc if {![regexp "^${_wspc}$" $data]} { puts "==> (Data 'update') '$data'" update } } proc HandleError {errcode errmsg} { puts "==> (Error) errcode=$errcode, errmsg=$errmsg" return -code error {I think we quit here} } set p [xml::parser] $p configure -final 0 -elementstartcommand HandleStart \ -elementendcommand HandleEnd -characterdatacommand HandleText \ -errorcommand HandleError set data1 {<stream><base>Some text here</base><junk chop='off' } set data2 {type='public'/><cut>more stuff</cut></stream>} after idle [list $p parse $data2] $p parse $data1 #after idle [list wrap::parsereentrant $p $data2] #wrap::parsereentrant $p $data1 #- FIX SCRIPT ---------------------------------------- namespace eval wrap { # A reference counter for reentries. variable refcount 0 # Stack for xml. variable stack "" } proc wrap::parsereentrant {p xml} { variable refcount variable stack incr refcount if {$refcount == 1} { # This is the main entry: do parse original xml. puts "++> main entry: refcount=$refcount" $p parse $xml # Parse everything on the stack (until empty?). while {[string length $stack] > 0} { puts "++> parse stack" set tmpstack $stack set stack "" $p parse $tmpstack } puts "++> main exit: refcount=$refcount" } else { # Reentry, put on stack for delayed execution. puts "++> reentry: refcount=$refcount" append stack $xml } incr refcount -1 return {} } |
|
From: Cameron L. <cl...@st...> - 2002-07-12 00:20:08
|
> From tcl...@li... Wed Jul 10 04:55:14 2002 > . > . > . > i have been asked to install some packages on one of our development-servers > (i am just a little sysadmin), now i have some questions concerning this, as > far as the probability that our developers may not be able to do their work > has to be reduced: > the packages that have to be installed are: > SOAP4Tcl > TclXML > TclDOM > currently, we have no tk-package on the specific server, just tcl 8.2, the > os is solaris, wish cannot be used, for there is no "cde" on the server. > what is needed under these circumstances to install the packages > successfully? (i'd prefer compiling the packages - there is also no compiler > on the server, but the packages could be compiled on another netra) > . > . > . I understand your preference to compile your own installation. My first recommendation, though, is that you download and install ActiveState's freely available ActiveTcl binary for Solaris <URL: http://www.activestate.com/Products/Download/Get.plex?id=ActiveTcl&a=e >. It includes all the packages you require (and more). If you insist on generating your own executable and binaries, see <URL: http://wiki.tcl.tk/1560 > <URL: http://wiki.tcl.tk/TclXML > <URL: http://wiki.tcl.tk/TclSOAP > for locations. |
|
From: Pagano S. <Sil...@je...> - 2002-07-10 09:19:28
|
hi! i have been asked to install some packages on one of our development-servers (i am just a little sysadmin), now i have some questions concerning this, as far as the probability that our developers may not be able to do their work has to be reduced: the packages that have to be installed are: SOAP4Tcl TclXML TclDOM currently, we have no tk-package on the specific server, just tcl 8.2, the os is solaris, wish cannot be used, for there is no "cde" on the server. what is needed under these circumstances to install the packages successfully? (i'd prefer compiling the packages - there is also no compiler on the server, but the packages could be compiled on another netra) thank you in advance! silvia |
3 messages has been excluded from this view by a project administrator.
![http://www.mealstogo.com/logo500.gif"](http://www.mealstogo.com/logo500.gif"){kind=link}
![http://www.mealstogo.com/burger1.jpg"](http://www.mealstogo.com/burger1.jpg"){kind=link}
![http://www.mealstogo.com/ctogo.gif"](http://www.mealstogo.com/ctogo.gif"){kind=link}
![http://www.mealstogo.com/soup1.jpg"](http://www.mealstogo.com/soup1.jpg"){kind=link}