Thread: Error on Ubuntu/Linux but not Windows :O!

Hello again!

Well, I've now moved to Ubuntu x64, but still I'm working with my team on a Windows/DirectX project, so I use MingW32.
Now, Elysia (Who uses Windows) Doesn't get these errors I get, I'm worried MingW32 doesn't have the same std:: functions, but I don't know, and that's why I'm asking these boards... So, grant me thy knowledge o' great cboard! xP
Thanks in advance!

My knowledge says: User Error.

But, seriously, what are you going on about? You need to post, at the very least, an error, a code segment that works-in-windows-but-not-linux, or... something. Otherwise, it's a claim with no proof.
That, and MinGW's stable compiler is gcc/g++ 3.4.5. If you're in Linux, I should honestly hope you're using something newer. Much newer. The difference in versions, could, at the very least, explain what you're seeing. (More likely however, is that it is you who is at fault...)

Woops! I was supposed to post that xD
And if I use GCC with the MingW compiler I get LOADS of cstdio.h errors, which I guess mean that there are the same definitions of stuff in GCC as MingW, but I don't know, anyways!

Code:

Error.h|10|error: no matching function for call to ‘std::exception::exception(const char*)’|

Ok, fixed by using

Code:

 std::runtime_error

instead of

Code:

 std::exception

LOADS of cstdio.h errors

stdio.h or cstdio. Either way, you probably shouldn't get errors from here.

Code:

Error.h|10|error: no matching function for call to ‘std::exception::exception(const char*)’|

There is no such constructor. exception is essentially a base class. (It has only a copy ctor, assignment, destructor, and what()) Using std::runtime_error is probably good for small stuff, for larger stuff you might want to think about your own classes, derived from std::exception.

The thing is, std::exception works for Windows Visual Studio xP I don't want to be forced to go back to Windows, I kinda like Ubuntu xD

Wow, and I thought that g++'s headers were hard to read...

Just reading headers, it would appear that VC++ might let you call exception(const char *). I don't use VC++ that much, but it would appear that (at least VS 8) comes with a non-standard <exception> header. I might have to test when/if I ever reboot to Windows.

Your solution of using runtime_error (or some other exception class - the STL provides a few) is a good one - stick with it. Additionally, it should work with VC++.

Dang it, Microsoft! They truly and really need to point out what headers are Microsoft-specific! -_-

Well, the header is standard, but its contents aren't.

They failed to mention that, too...