PDcurses incompatibility with fstream.h?

On Tue, 04 Apr 2006 15:31:20 -0700, kobuscrispi wrote:

[snip]

> I wanted to use fstream.h for the file input/output. However, as soon
> as I include it, I get *72* errors! Further investigation revealed that
> most, if not all, of these errors were caused by the fact that curses.h
> and fstream.h both try to define a function called clear(). Is there
> any way to get these two files to coexist peacefully?

The problem probably isn't exactly caused by the function clear(), it's
likely caused by the macro of the same name. The easiest way to fix it is
to

#undef clear

after including [n]curses.h.

For convenience, a lot of the functions dealing with stdscr in curses.h
are macros to the actual [mv]w{foo} functions.

<fstream.h> is an old c++ header though - you might be better off moving
to the new <fstream> style.

Cheers,
Adam
 >> Stay informed about: PDcurses incompatibility with fstream.h? 

To be honest, I wasn't even aware that there was any functional
difference between <fstream.h> and <fstream>. But now I know!

How are they different, exactly?
 >> Stay informed about: PDcurses incompatibility with fstream.h? 

kobuscrispi DeleteThis @gmail.com schrieb:
> How are they different, exactly?

Just that the .h includes are deprecated, I think for all the standard
headers. There's no real way you would know unless someone told you.
There should be no functional difference, though, except if you
distributed your code my compiler would force me to change it manually.

--
Jim Strathmeyer
 >> Stay informed about: PDcurses incompatibility with fstream.h? 

On Wed, 05 Apr 2006 11:02:37 -0500, Jim Strathmeyer wrote:

[ <fstream> vs <fstream.h> ]

> kobuscrispi.TakeThisOut@gmail.com schrieb:
>> How are they different, exactly?
>
> Just that the .h includes are deprecated, I think for all the standard
> headers. There's no real way you would know unless someone told you.

Well, that's true for the c-style headers. So for <string.h> for example,
the only difference between <cstring> and <string.h> is that all entities
in <cstring> are only in the std:: namespace, whereas they're in both
the std:: and the global namespaces for <string.h>.

Of course there are exceptions, such as the "float abs(float, float)"
overload in <cstdlib> which doesn't appear in <stdlib.h>.

> There should be no functional difference, though, except if you
> distributed your code my compiler would force me to change it manually.

For <fstream> though, and this is true of almost the entire <iostream>
hierarchy, there are differences. Older versions used strstreams
(often shortened to <strstrea.h>), which were char * based rather than
modern stringstreams.

Moral: You're using the modern library and getting better support if you
use the modern style rather than relying on the deprecated headers and
library support.

Cheers,
Adam
 >> Stay informed about: PDcurses incompatibility with fstream.h?