why is operator overloading for << so BROKEN

[Popping mad]

I have a series of data structures that I wanted to display information on using operator overloading for operator<< and it has proven to be impossible!!

why is it so broken

It can't even decide if a "string" is a *char or a something else and just bombs.

It is not usable.

[Wouter van Ooijen]

Op 08-Nov-16 om 12:44 PM schreef Popping mad:

Which is in sharp contrast with your post, which constains a wealth of
details, so now we all know exactly what you exepected of operator<<,
what you observed, and what the cause is.

Thank you so much for including all the details!

Wouter "Objects? No Thanks!" van Ooijen

[Öö Tiib]

On Tuesday, 8 November 2016 13:44:32 UTC+2, Popping mad wrote:
> I have a series of data structures that I wanted to display information
> on using operator overloading for operator<< and it has proven to
> be impossible!!

No, it is doable. Ignorance may pass with time. Try again.

>
> why is it so broken

Your code is broken because you wrote it that way and respond arrogantly
when others try to help you. Try again.

>
> It can't even decide if a "string" is a *char or a something else
> and just bombs.

That does not parse. Nothing in C++ is *char so compiler does not
even need to consider if something is *char.

>
> It is not usable.

This Fox has a longing for grapes:
He jumps, but the bunch still escapes.
So he goes away sour;
And, 'tis said, to this hour
Declares that he's no taste for grapes