Jump to content
  • Advertisement
Sign in to follow this  
relpats_eht

Expected unqualified-id in standard headers.

This topic is 4530 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Well, I seem to have hit a bit of a problem. After making major structrual and design changes to some GUI code, it no longer properly compiles. I continually get the expected unqualified-id error. While normally this would be no problem, the error has been popping up in standard headers, such as assert, fstream, etc. To the best of my knowledge, in theory, header order for standard headers shouldn't matter, but in practice, it does, and I need to reorder them, however, I can't seem to find an order in which I don't get the error in any standard header. Fixing it for one causes it to pop up in another. I have gone through the code to try to come up with a list by which headers are called (duplicates not included), hopefully someone here can tell me a proper way to order them so this error will cease. Thank you.
#include <allegro.h>
#include <alleggl.h>
#include <GL/glu.h>
#include <vector>
#include "MathUtils.h"
 - #include <cmath>
 - #include <cstdlib>
 - #include <iostream>
#include "XMLUtils.h"
 - #include "tinyxml.h"
   - #include <cctype>
   - #include <cstdio>
   - #include <cstdlib>
   - #include <cstring>
   - #include <cassert>
   - #include <string>
   - #include <iostream>
 - #include "GenUtils.h"
   - #include <sstream>
   - #include <fstream>
Also, with this current orientation, it is cassert which is causing problems.

Share this post


Link to post
Share on other sites
Advertisement
Are you using VC++ 7.1 or better, perchance?

In your project settings, under Advanced, choose "Show Includes"... and the filenames will output in the order they are included in the Output pane.

Perhaps it is your application code that re-defines a global operator, or something?

What you describe sounds like what happens if you include Paul Nettle's memory manager BEFORE (specifically) <xdebug>


C

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!