Delphi XE 中不再有 xercesxmldom 单元吗?
我想知道作为 之一的 xercesxmldom
单元发生了什么XML DOM 实现。
它似乎在 Delphi XE 中消失了。
为什么?
(我搜索了文档;找不到有关 xercesxmldom 消失的任何相关信息)。
编辑:这些是我存档的源:
R:\>dir /s /b xercesxmldom.pas
R:\D2006-Enterprise-D10-BDS-4.0\source\Win32\xml\xercesxmldom.pas
R:\D2007-Enterprise-D11-RadStudio-5.0\source\Win32\xml\xercesxmldom.pas
R:\D2009-Enterprise-D12-RadStudio-6.0\source\Win32\xml\xercesxmldom.pas
R:\D2010-Enterprise-D14-RadStudio-7.0\source\Win32\xml\xercesxmldom.pas
R:\D7.01.Architect\Source\Xml\xercesxmldom.pas
R:\DXE-Enterprise-D15-RadStudio-8.0
源树中没有任何内容...
--jeroen
I'm wondering what happened to the xercesxmldom
unit as one of the XML DOM implementations.
It seems to have disappeared in Delphi XE.
Why?
(I searched the docs; couldn't find any relevant info on xercesxmldom disappearing).
Edit: these are the sources I have archived:
R:\>dir /s /b xercesxmldom.pas
R:\D2006-Enterprise-D10-BDS-4.0\source\Win32\xml\xercesxmldom.pas
R:\D2007-Enterprise-D11-RadStudio-5.0\source\Win32\xml\xercesxmldom.pas
R:\D2009-Enterprise-D12-RadStudio-6.0\source\Win32\xml\xercesxmldom.pas
R:\D2010-Enterprise-D14-RadStudio-7.0\source\Win32\xml\xercesxmldom.pas
R:\D7.01.Architect\Source\Xml\xercesxmldom.pas
Nothing in the R:\DXE-Enterprise-D15-RadStudio-8.0
source tree...
--jeroen
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这是答案的引用Bruneau (Jean-Marie) Babet 发布到 我在 Embarcadero 论坛上的问题:
因此,如果您在 Delphi 中使用 xerces,那么要么等待包装器出现在 sourceforge 上,要么切换执行 OpenXML ADOM 与 Delphi XE 兼容。
Here is a quote the answer that Bruneau (Jean-Marie) Babet posted to my question on the Embarcadero forums:
So if you are using xerces in Delphi, then either wait for the wrappers to appear on sourceforge, or switch do the OpenXML ADOM which is compatible with Delphi XE.
它在我安装的 RAD Studio
XE2010 中。源文件位于:我在 XE 的源路径中的任何地方都没有看到它,所以看起来他们确实出于某种原因删除了它。
然而,快速扫描 2010 版本中的源代码并没有发现任何阻止它在 XE 中使用的内容。不过,我还没有测试过。
It's in my install of RAD Studio
XE2010. The source file is in:I don't see it in XE's source path anywhere, so it does appear they've removed it for some reason.
A quick scan of the source code in the 2010 version, however, doesn't reveal anything that would prevent it's being used in XE. I haven't tested that, however.