The use of ATL COM

Started by
0 comments, last by jesterlecodeur 22 years, 4 months ago
Is it good to use the ATL COM wizard or there is a performance drawback (i mean in in-proc w/ C++)? Is it a good idea to want to make complete COM components ? Does the .Net give a better choice? Why English rules?? C pas très malin tout ça!
_______________
Jester, studient programmerThe Jester Home in French
Advertisement
quote:
Is it good to use the ATL COM wizard
[/source]
Absolutely. The ATL will give you no perform hit what-so-ever (no more than the COM overhead anyway)

If you want need/want language independence nor need/want threading-model independence don''t use COM. Learning how COM works is still a decent idea, as it is a pretty good OO design to accomplish it''s goals.

I have yet to seriously use .Net so I can''t make any reliable statements about how it truely compares to COM. It sounds like a better/easier/more integrated solution (but it offers no additional capibilities - COM and .Net objects are inter-exchangable).


Magmai Kai Holmlor
- Not For Rent
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara

This topic is closed to new replies.

Advertisement