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] Wed Sep 20 03:32:53 -0700 
2006 -------
@sb:

1) What I meant was to define a typedef for sal_Unicode that corresponds to what
is defined in Windows headers for WCHAR (This should be unsigned short for 
mingw).

If (and I don't know as nobody @ sun ever tested it) the gcc in mingw has a bug
and a typedef based on a type that is a typedef itself may confuse the gcc it
would help to define a typedef to unsigned short for sal_Unicode directly.

But if the gcc works well I can't see any reason why the casts are necessary at 
all.

The only reason that would make those casts necessary is a bug in gcc or a
typedef for WCHAR in the mingw windows headers that uses a different 16 bit data
type, f.e. signed short or a struct. But I can't imagine this because it would
be a really silly idea as it would be predictible that many code written for the
Microsoft compiler won't compile are more worse would behave different (f.e.
when using a signed short for WCHAR).

2) Yes as it is nearly the same and not type safe. ;-)

---------------------------------------------------------------------
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