Thread: Input class

Originally Posted by CornedBee

Code:

#ifndef TCHAR
	#ifdef UNICODE
		#define TCHAR wchar_t
	#else
		#define TCHAR char
	#endif
#else
	#define TCHAR char
#endif

Dangerous. windows.h handle the TCHAR issue with a typedef, not a macro, so your #ifdef won't trigger. (windows.h defines _TCHAR_DEFINED, but I wouldn't rely on it.)
Since a typedef would be scoped anyway, just make it a typedef.

Hmmm.
OK, I changed that a bit.

Now the only problem would be the operators...
Should they cast? Should they not?
Perhaps they should complement the member functions (both throw & non-throw).
And I wouldn't have the slightest clue how to return a "bad stream" in case they fail.

>> And I wouldn't have the slightest clue how to return a "bad stream" in case they fail.

You shouldn't need to "do" anything. Your run-of-the-mill insertor/extractor ...

Code:

std::ostream & operator<< (std::ostream & out, const object & o )
{
  out << o.foo();
  out << o.bar();
  return out;
}

If foo and bar return plain old data then there is no problem, the state of the stream is determined by the success or failure of the conversion. If foo and bar do not return plain old data then the state of the stream is determined by the result of operator << for the object.

It would be better if you understood that by default streams do not throw.

If you want a specific state to be exceptional you usually call exception( mask ); beforehand.

The problem is that I don't return a stream, but rather the "input object." I'd have to define some "bad" state implementation I guess.
Along with a throw-version and a non-throw version of the operator equivalent member functions.