Bug 469028 - Compilation error because of a C++ keyword in /usr/include/real_exception_file.h
Compilation error because of a C++ keyword in /usr/include/real_exception_file.h
Product: Fedora
Classification: Fedora
Component: libFoundation (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Axel Thimm
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-29 11:31 EDT by Andrea Tassotti
Modified: 2009-07-31 13:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
libFoundation-1.1.3-10.fc6 Same package for FC7 and FC8. No fix available upgrading to FC8.
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 01:48:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Example source code (93 bytes, text/plain)
2008-10-29 11:33 EDT, Andrea Tassotti
no flags Details

  None (edit)
Description Andrea Tassotti 2008-10-29 11:31:27 EDT
Example source code

Description of problem:
Error compiling .mm (ObjC + C++ code) source using Foundation.h.

Version-Release number of selected component (if applicable):

How reproducible:
Compiling a simple .mm source importing <Foundation/Foundation.h>

Steps to Reproduce:
1.Use example.mm file attached to this report
2.g++ -lobjc -lFoundation example.mm

Actual results:
/usr/include/real_exception_file.h:68: error: expected identifier before
/usr/include/real_exception_file.h:68: error: expected `:' before ‘;’ token
/usr/include/real_exception_file.h:68: error: expected identifier before ‘;’

Expected results:
Compilation without errors

Additional info:
identifier "class" MUST be any of "aClass", "clazz", "X" or other
NON-CPP-KEYWORD for use in ObjC/C++ ibridation.
Comment 1 Andrea Tassotti 2008-10-29 11:33:07 EDT
Created attachment 321814 [details]
Example source code
Comment 2 Andrea Tassotti 2008-10-29 11:34:50 EDT
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Same package for FC7 and FC8. No fix available upgrading to FC8.
Comment 3 Bug Zapper 2008-11-26 06:16:08 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-01-09 01:48:42 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.