Do we officially support .Net2003 in current DEV300 development? Reason
I'm asking is http://www.openoffice.org/issues/show_bug.cgi?id=97555 that it seems can be fixed only by making some member public instead of
private, which if needed in the official code line I would do only for
that specific _MSC_VER value. If we don't support .Net2003 Pavel could
apply a patch on the fly during his builds.
OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [hidden email] account, which I use for
mailing lists only and don't read from outside Sun. Use [hidden email] Thanks.