Doug Turner wrote:
> Adrian Herscu wrote:
>
>> Hi all,
>>
>> I have some COM background, and I'm interested to learn more about XPCOM.
>>
>> So far, I understand that XPCOM stands for Cross Platform COM.
>> But, I didn't understand what this really means.
>>
>> How exactly the "Cross Platform" goal is achieved?
>> Or, in other words, what rules should I obey (as a XPCOM componet
>> programmer) in order to build a "Cross Platform" component?
>
>
>
> Components that are compiled are required to be recompiled on each
> target platform. This means that any functionality that is platform
> dependent will require you to rewrite that part. Components can be
> implemented in a scripting language such as Javascript may be
> distributed onto different platforms without any modifications.
>
> The truth is that effort does go into thinking about cross platform
> implications when writing a component. Most things have been pretty
> well abstracted by XPCOM, but when writing a component, you will have
> places that may be #ifdef per platform.
>
> Hope this helps,
>
> Doug Turner
> [EMAIL PROTECTED]
>
>
So, write-once & run anywhere (WORA) is true only for JavaScript XPCOM
components?
When I am implementing a XPCOM component in a compiled language (like
C++), I have to maintain n platforms just for the compiling & linking
process (and it doesn't matter if that component makes platform
dependent calls!).
Can I make a XPCOM component to run on a JVM? Is there a bridge between
JVMs and XPCOM?
