Issue 8205 - sfx2/source/bastyp/progress.cxx - doesn't compile with gcc-2.95
Summary: sfx2/source/bastyp/progress.cxx - doesn't compile with gcc-2.95
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: 643
Hardware: SGI IRIX
: P3 Trivial (vote)
Target Milestone: ---
Assignee: sander_traveling
QA Contact: issues@porting
URL:
Keywords: merge_pending
Depends on:
Blocks:
 
Reported: 2002-10-10 08:35 UTC by nickb
Modified: 2003-03-24 08:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
sfx2/source/bastyp/progress.cxx - re-order to avoid confusion (665 bytes, patch)
2002-10-10 08:39 UTC, nickb
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description nickb 2002-10-10 08:35:34 UTC
/build1/nickb/openoffice/workarea/SRX643_OO/sfx2/source/bastyp/progress.cxx: In
method `void SfxProgress_Impl::Enable_Impl(unsigned char)':
/build1/nickb/openoffice/workarea/SRX643_OO/sfx2/source/bastyp/progress.cxx:217:
ambiguous overload for `BOOL & ? int : SfxObjectShellRef &'
/build1/nickb/openoffice/workarea/SRX643_OO/sfx2/source/bastyp/progress.cxx:217:
candidates are: operator ?:(bool, SfxObjectShellRef, SfxObjectShellRef) <builtin>
/build1/nickb/openoffice/workarea/SRX643_OO/sfx2/source/bastyp/progress.cxx:217:
                operator ?:(bool, SfxObjectShell *, SfxObjectShell *) <builtin>
dmake:  Error code 1, while making '../../unxirgm.pro/slo/progress.obj'
Comment 1 nickb 2002-10-10 08:39:23 UTC
Created attachment 3118 [details]
sfx2/source/bastyp/progress.cxx - re-order to avoid confusion
Comment 2 nickb 2002-10-31 00:36:10 UTC
Confirming Issue.
Comment 3 foskey 2002-12-16 13:41:33 UTC
Applied to OO643C branch.
Comment 4 michael.bemmer 2003-03-24 08:37:51 UTC
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.
Comment 5 michael.bemmer 2003-03-24 08:51:58 UTC
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.