"Tolkin, Steve" wrote:
>
> The failure was that make test from anyData shows
> AnyData
> XML ...
> and then it hangs.
I've had another report of the XML test hanging, but haven't been able
to reproduce it yet. I'll look into it and get back to you.
> But some of the Twig tests failed.
> Is this the problem?
Could be.
> I also tried to install XML::Parser myself
> and got a problem compiling. But it *seems* that Twig only needs
> the XML::Parser interface, not any of the code. Is that true?
You defintiely need XML::Parser fully installed. I'm pretty sure it
should be on activeState.
> 2. A separate question. While attempting to diagnose the problem
> I see that the new method in XML.pm says:
> if ($self->{col_names}) {
> ## something goes here :-)
> }
I am a sloppy coder :-(. I leave notes to myself. Real specific ones
like that so I can remember what I meant when I wrote it. What can I
say? :-)
> This looks like it needs to be fixed for me to provide my own names,
> which I need to do. Is that correct?
Well, mostly true (and I am working on it), but for now if you either
include a DTD in the file or supply one as a flag {dtd=>$dtdStr), the
column names will be taken from the DTD. If you omit column names that
are in the file from the DTD, they won't be treated as columns. If
that doesn't do the trick for you or you have some other type of needs
for the column names, please let me know so I can see if I can support
them in the next release.
> 3. I replied to the email lists, rather than just Jeff, in case
> another user or developer hit a problem like this, or could
> benefit from my experience. But I would be willing to move
> this discussion elsewhere if we can agree on where.
If folks don't want this level of specificity on the dbi lists, it's
fine with me to do it via private email and I can report the outcome
back to the list.
--
Jeff
