This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: display in a recursive way
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: display in a recursive way
- From: Andrew Kimball <akimball at microsoft dot com>
- Date: Wed, 26 Apr 2000 15:36:19 -0700
- Reply-To: xsl-list at mulberrytech dot com
Paulo,
Your description of the xsl:copy bug has sparked my curiosity. Can you
directly send me a repro? I'll take a look at it.
Also, I think you can e-mail bugs to xmlfb@microsoft.com rather than posting
them to the MSXSL newsgroup.
~Andy
-----Original Message-----
From: Paulo Gaspar [mailto:Paulo.Gaspar@krankikom.de]
Sent: Wednesday, April 26, 2000 2:38 PM
To: xsl-list@mulberrytech.com
Subject: RE: display in a recursive way
Thanks Jonathan.
As much as I enjoy joking with the M$ nickname I respect your team's work
with msxml.
Whatever prejudice I might have is related with often marketing bended
technical information in Microsoft's web site. Anyway, it is easy to get
that sentence out of context and get enthusiastic... and then disappointed
(as I did).
Another issue I would like to ask: is any mail address available for bug
report?
I detected a few unlisted bugs and I find the newsgroups a bit slow most
of the time. I would prefer to report them to some mail address.
Just to avoid misunderstandings from the list about the bug gravity, I
consider the product very stable and useful for a beta. Some problems I
found in MSXML 3 are like:
- Silent XSLT processor behavior on error (syntax and others) detection
(does not produce anything instead of raising an error);
- Empty silent result using a sequence of <xsl:copy... with overlapping
node sets.
(I have a few other doubts, including repeated nodes returned by id() for
a repeated list of IDs and so.)
However:
- Missing to raise exceptions is a typical maturity problem and MSXML3
does it less than many commercially released products (it does NOT
happen on every error);
- The "<xsl:copy..." feels like an optimization that backfired. Same
as previous.
But MSXML processes quite some volumes of XML with quite some SPEED and
stability (doesn't explode all the time) and I am very happy about that.
(IE5 browser, full fixes, behaves much worse has a COM component.)
Just to be fair on MS(Would anyone use it if it was that bad?)XML:
I could not use "life" any another solution I know of with the ease
(nice COM interface) and speed I enjoy now.
There is still a long way to go for the product, but those that use it
should remember also the positive points. (Should we go on talking
about the many Java alternatives and the need for more CPU power... or
talk about "nice" C/C++ based solutions?)
I am not a Microsoft fan, and I programmed a lot in C and C++. But
there are other tools which versatility and ease of use are a bit more
interesting.
(Hint - Borland Delphi, the tool that M$ avoids referring to... while
trying to implement its feature list in VB7.
I respect quite a few technical teams in Microsoft Jonathan, but not
the marketing guys... not the marketing guys.)
Best regards,
Paulo
-----Original Message-----
> -----Original Message-----
> From: Paulo Gaspar [mailto:Paulo.Gaspar@krankikom.de]
> I have been using MSXML3, which is in beta. Even in MSXML3
> (although M$
> states that the XPath spec is now completely implemented), the sibling
> axis of XPath is not implemeted. So... the error you get is
> due to MSXML
> not knowing the "following-sibling" instruction.
I suppose that you are referring to the statement on our web site that the
March release includes "complete XPath function support", which is intended
to indicate that we have implemented the remaining XPath built-in functions
not already implemented in the previous web release, not that we have
complete XPath support. We'll try to make this clearer next time.
- Jonathan Marsh
Microsoft
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list