Hi all,

I would like to comment as a weekend programmer.

In message "[dev] The evil that is cppu::getCaughtException",
Stephan Bergmann wrote...
 >I do not see any elegant solution for this problem.  Potential but ugly 
 >solutions would include:

IMHO although all four options are ugly, the fourth option is only viable and 
realistic.

 >- Remove all calls of the---dangerous anyway---cppu::getCaughtException 
 >from the OOo code base 
 >(<http://lxr.go-oo.org/ident?i=getCaughtException> lists "245 references 
 >in 102 files").

It will be very difficult as we have to completely redesign bridge 
functionality.

 >- Make sure the relevant compiler runtime libraries will always be 
 >installed system wide when running OOo.  (This had been discussed 
 >before, but dismissed.)

It can be broken by other programs.

 >- Use only compilers for which runtime libraries need not be installed 
 >either syste wide or next to every DLL that uses them (e.g., older 
 >Microsoft compilers, or GCC).
 
As you are aware, MinGW port is still experimental and have problems with COM 
and 
ATL.

And as obo pointed out, older microsoft compliers have problems with Vista.

 >- Turn the Three Layer Office back into a Two Layer Office, where the 
 >URE and Basis layers are united (and the above scenario would again only 
 >use one instance of msvcr90.dll loaded into the process, and everything 
 >would probably work fine; there is also an instance of msvcr90.dll in 
 >the Brand layer, but that should not interfere with any 
 >cppu::getCaughtException calls).

Regards,

Takashi Ono ([EMAIL PROTECTED])

----
 Takashi Ono(HK Freak)
 mailto:[EMAIL PROTECTED] or [EMAIL PROTECTED]
        (Personal Address, checked every morning/evening and holidays)
 mailto:[EMAIL PROTECTED]
        (Address for business, checked every working days)
 http://www.hkfreak.net

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to