To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=53572





------- Additional comments from [EMAIL PROTECTED] Fri Dec 16 16:42:56 -0800 
2005 -------
@dbo:
[EMAIL PROTECTED] wrote...
 >IMO I expect little changes when porting to a gcc-compiled platform, except 
for
 >system layer programming (i.e. sal, tools) and makefiles. If there are 
further
 >problems in C++ modules, this indices wrong system layer adoptions, e.g. like
 >the wrong mapping of sal_Unicode that we already figured out. Finally, please
 >leave the alloca() occurences as is, the next mingw will hopefully fix this, 
too.

Do you mean that we should patch all the sources that is using MS unicode 
WINAPI without using sal? I am checking them again on src680, but 
unfortunately there are so many. There are two strategies.
1) Using reinterpret_cast.
2) Enrich sal and use it.
On older platform I was using 1) but 2) seems to be better. But sal peaple may 
not like to make interface fat for windows specific modules. I would like to 
get comments from the people involved in sal.

The immediate fix for alloca and unwinding problem is not so hopeful, I think. 
Mingw people are not handling the bugs inherited from gcc, and gcc people may 
not focus on the bugs only on non-dwarf2 platforms. Moreover, their focus is 
now on version 4.x.x.
I am checking out modules include both sal/alloca.h and catch() and they are 
not so many, maybe only in bridges.

tono (Takashi Ono)


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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

Reply via email to