On Sat, Nov 1, 2014 at 11:34 AM, wrote:
> What a terrible news! I have many C++ XPCOMs evaluating xpath expressions.
> They must be coded in C++ for high speed.
Given the modern JIT and DOM bindings, I am very doubtful that you will
encounter JS-based or binding-based bottlenecks for xpath expr
在 2014年11月1日星期六UTC+8下午5时58分46秒,Bobby Holley写道:
> I think you're probably out of luck - the method was de-COMed, and is now
> not accessible from external C++ code.
>
> In generally, using nsIDOM* interfaces from external applications is
> explicitly not supported. If you want to do DOM stuff, you
I think you're probably out of luck - the method was de-COMed, and is now
not accessible from external C++ code.
In generally, using nsIDOM* interfaces from external applications is
explicitly not supported. If you want to do DOM stuff, you should do so
from JS, and communicate with your JS code u
在 2014年11月1日星期六UTC+8下午4时40分57秒,David Rajchenbach-Teller写道:
> I believe that the methods have migrated to
>
> http://dxr.mozilla.org/mozilla-central/source/dom/xslt/xpath/XPathResult.h?from=XPathResult#47
>
> Cheers,
> David
>
> On 01/11/14 08:43, fuller...@gmail.com wrote:
> > Hi,
> >
> > Xulr
I believe that the methods have migrated to
http://dxr.mozilla.org/mozilla-central/source/dom/xslt/xpath/XPathResult.h?from=XPathResult#47
Cheers,
David
On 01/11/14 08:43, fuller...@gmail.com wrote:
> Hi,
>
> Xulrunner 33.x is different from the former releases. I cannot compile my C++
> XPCO
Hi,
Xulrunner 33.x is different from the former releases. I cannot compile my C++
XPCOMs because the new interface of nsIDOMXPathResult has not the methods to
get the values.
What should I do?
___
dev-platform mailing list
dev-platform@lists.mozilla.o
6 matches
Mail list logo