I might suggest having a look at https://wiki.mozilla.org/Gecko:Overview
for your general architectural questions.
On Sun, Jul 23, 2017 at 12:00 AM, Enrico Weigelt, metux IT consult <
enrico.weig...@gr13.net> wrote:
> Hi folks,
>
>
> could anyone please give me some insight, where the the IDLs
>
On 24.07.2017 02:18, Boris Zbarsky wrote:
Hi,
Brief summary. IDL:
1) Generates xptcall information for xpconnect to allow calling from JS
and into JS (via synthetic vtables).
2) Generates headers that declare pure virtuals.
3) Is used for defining XPCOM interfaces.
(you can do just #2 wit
On 7/23/17 9:58 PM, Enrico Weigelt, metux IT consult wrote:
what's the difference between idl and webidl ?
Brief summary. IDL:
1) Generates xptcall information for xpconnect to allow calling from JS
and into JS (via synthetic vtables).
2) Generates headers that declare pure virtuals.
3)
On 24.07.2017 00:11, Enrico Weigelt, metux IT consult wrote:
what's the difference between idl and webidl ?
I've noticed that webidl's seem to support preprocessor directives
(eg. #ifdef), while the others dont.
--mtx
___
dev-platform mailing list
d
On 23.07.2017 18:15, Botond Ballo wrote:
could anyone please give me some insight, where the the IDLs
(and the code generated from them) are actually used ?
Javascript bindings ?
They are typically used as an interface between C++ and JS code.
Ah, what I've already suspected.
While trying t
> could anyone please give me some insight, where the the IDLs
> (and the code generated from them) are actually used ?
>
> Javascript bindings ?
They are typically used as an interface between C++ and JS code.
As an example, consider nsIDocShell.idl [1]. This defines an interface
named "nsIDocSh
6 matches
Mail list logo
