Ticket #16967

#include files clash when adding standard C++ includes

Open Date: 2009-05-27 04:05 Last Update: 2009-06-18 05:30

Reporter:
Owner:
(None)
Type:
Status:
Open
Component:
(None)
MileStone:
(None)
Priority:
3
Severity:
5 - Medium
Resolution:
None
File:
None

Details

It seems that the large number of include files, particularly those that include other include files, are causing problems when trying to add standard C++ includes - like #include <iostream>.

(Actual cause of problems may be different)

In any case alterations to any of the include files appears to be very sensitive.

Ticket History (3/6 Histories)

2009-05-27 04:05 Updated by: paulblay
  • New Ticket "#include files clash when adding standard C++ includes" created
2009-06-12 19:21 Updated by: paulblay
Comment

Possibly they need to be included like

 extern "C"
 {
 #include "c-stylefile.h"
 }

?

2009-06-14 02:25 Updated by: csartanis
Comment

Depends what you're trying to do with this. iostream wont be too useful because all input/output is already done through angband utility functions that are hooked into port-specific UIs. What other libraries do you want to use?

2009-06-14 02:44 Updated by: paulblay
Comment

Basically two (low priority) points.

1. I wanted to 'have the option' if needed. 2. In my ongoing (er, just started) efforts to learn C++ I wanted to be able to make the code look "more like C++ should", IYKWIM.

2009-06-17 01:44 Updated by: paulblay
Comment

Er, maybe it's just because the files aren't really C++ files until they have the .cpp extension. (D'oh!).

2009-06-18 05:30 Updated by: paulblay
  • Priority Update from 6 to 3

Attachment File List

No attachments

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login