"Orchid XP v7" <voi### [at] devnull> wrote in message 
news:4728ece4$1@news.povray.org...
> So... can anybody provide a high-level overview of the general 
> structure and terminology of this stuff?
>
> (All the documentation I found so far just shows examples in C - 
> which means nothing to me.)

http://en.wikipedia.org/wiki/Component_object_model

Also - powershell from MS is free and does COM

Post a reply to this message

pan wrote:
> "Orchid XP v7" <voi### [at] devnull> wrote in message 
> news:4728ece4$1@news.povray.org...
>> So... can anybody provide a high-level overview of the general 
>> structure and terminology of this stuff?
> 
> http://en.wikipedia.org/wiki/Component_object_model

Already read it. It's one of Wikipedia's less helpful articles. (Ditto 
for all that .NET stuff.)

> Also - powershell from MS is free and does COM 

Um... OK. Maybe they have some documentation I can use...

Post a reply to this message

Invisible wrote:
> Um... OK. Maybe they have some documentation I can use...

I think it's more like, now that you know what it is (namely, an API for 
communication between independent objects via an API-like interface), 
what's your actual question? :-)

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message

Darren New wrote:
> Invisible wrote:
>> Um... OK. Maybe they have some documentation I can use...
> 
> I think it's more like, now that you know what it is (namely, an API for 
> communication between independent objects via an API-like interface), 
> what's your actual question? :-)

 From Wikipedia's article, it seems that COM's idea of what the terms 
"object", "class" and "method" mean is somewhat different from the usual 
OO terminology. (Or Wikipedia is outright incorrect, which is of course 
not impossible.) Can anybody clarify?

Post a reply to this message

> Darren New wrote:
>> Invisible wrote:
>>> Um... OK. Maybe they have some documentation I can use...
>>
>> I think it's more like, now that you know what it is (namely, an API 
>> for communication between independent objects via an API-like 
>> interface), what's your actual question? :-)
> 
>  From Wikipedia's article, it seems that COM's idea of what the terms 
> "object", "class" and "method" mean is somewhat different from the usual 
> OO terminology. (Or Wikipedia is outright incorrect, which is of course 
> not impossible.) Can anybody clarify?

It is a bit different from normal OO terms. Just wait until you get to 
the "containment/delegation and aggregation" part (replaces uses of 
inheritance), that's really screwed up.

Post a reply to this message