Thanks Mario Semo for your msg about Som Of The Time, on Friday,
10-14-1994!

MS> but you can use exception inside the implementation. And - how do
MS> you throw  an C++ exception from one machine to another one? My
MS> class  implementation runs under OS/2 on machine 1, but my clients 
MS> (users) run on other machines in the network. (even on  other HW /
MS> OS platforms. eg. RS/6000 with AIX). 

My point was that, if I want to use some SOM widget to make my life
easier (thats the point right?), but that widget does not support
exceptions and my entire architecture depends upon the exception
mechanism, then there's a bit of a problem. Sure I can use exceptions
within my own widget by implementing it in C++; but, if the point of
SOM is to be able to buy plug in components, then it falls short in
that area.

I don't understand what you are asking concerning the cross platform
exception throwing. Elaborate on that and I will try to answer.

MS> we have similar requirements. My customers are 
MS> organizations which built eg. the controlling systems for 
MS> power platforms. and doing something wrong in an atom power 
MS> plant means a lot of people being dead.
MS> 

So, would you buy (say) a SOM PID controller widget that you bought
from some company that you nothing about and plug into your system,
upon which lives depend? My main point was just that, that there are a
large set of systems out there that cannot benefit from the ability to
buy plug in modules (be they SOM or whatever) because there is no
consistent mechanism to mechanically validate such modules (i.e. there
are not enough defined standards, and the ability to implement each
widget in a different language just makes that worse.)

MS> huh? whats the relation of SOM2/DSOM with WPS? ok, WPS is a 
MS> SOM applikation (under OS/2 2.x with SOM1, under 3.x with 
MS> SOM2), but I'm using DSOM as an industry standard CORBA 
MS> ORB. (so i don't have to think about DCE, little endian/big 
MS> endian etc. problems).
MS> 
MS> talgient will not define ORB/persistent/... standards. 
MS> these are defined by OMG (CORBA ORB), ODBMG (OODB ODBG93), 
MS> OSF (DCE). Taligent will have implmentation of these 
MS> standards, but so do SOM2.
MS> 

I was just saying that little (basically standalone) WPS widgets are a
good use for SOM. And yes you are right about the DSOM thing. My guess
as to the reason that Taligent will soon use SOM (via CSet/2++'s
upcoming direct-to-SOM) is to leverage the object brokering. However,
you will still have to develop your entire Taligent in C++ (as far as I
can tell at this point in the beta) to leverage the inherent power of a
fully C++ system. So my original point that SOM's ability to use
multiple languages is not that big an advantage still holds.

___
 X KWQ/2 1.2b X "640K ought to be enough for anybody." - Bill Gates, 1981

--- Maximus/2 2.01wb