3 ms·
> OLE style The Oberon component model actually differs significantly from COM/OLE. Oberon uses messages and message protocols; COM uses interfaces and the sam
by Rochus 3y ago
> OLE style
The Oberon component model actually differs significantly from COM/OLE. Oberon uses messages and message protocols; COM uses interfaces and the same virtual function tables as C++. Also interesting to note that there is not a single type-bound procedure in the whole Oberon System release 2.3.6 code.
- pjmlp 3y agoStyle doesn't mean 100% the same C++ code as OLE. Of course the Document/Gadgets/Library system was implemented in a different way as OLE.
- Rochus 3y agoOLE 1 and Gadgets both appeared in 1990; Marais references the 1989 InterViews (Linton, Vlissides, Calder) publication in his 1990 report. See also https://doi.org/10.1080/10618600.1996.10474712 https://doi.org/10.1080/10618600.1996.10474712.
- pjmlp 3y agoYes Herr Professor, they appeared on the same year. I was trying to make a point about an idea for the people that might have heard of OLE and nothing else. How many with the age of 30 years and below do you think even know what InterViews was about?
- Rochus 3y agoIt is important and also helpful for the younger readers to name and correctly attribute the essential achievements. E.g. one fellow stated that "OLE was introduced in Windows 3.x", so it is important to note that the Oberon Gadget system appeared in the same year, and the component system was an independent achievement, that took a completely different approach than OLE or OpenDoc.