C++ ---> HTML

[Albatross]

@chrisname:
That's rather stupid that a C++ function wouldn't take C++ types as arguments, don't you think? :/

-Albatross

[chrisname]

No, I don't. std::fstream and std::string are separate libraries. A const char* is native, so it doesn't require a library to handle. That way, the libraries aren't inter-dependant.

[mcleano]

+1 chris.

[Bazzy]

IMHO it was a bad design choice, but IIRC that is going to be fixed in C++0x

[chrisname]

That's stupid. Now, to open a file, I have to include the string library too?

[blackcoder41]

bad design? why? o.O

[Bazzy]

That's stupid. Now, to open a file, I have to include the string library too?

Nope, it will be included in fstream

bad design? why? o.O

Because C++ strings are std::string, not char arrays

[blackcoder41]

that's why it has the method c_str(), is it still bad? so using containers like strings and vectors are bad design?

[Bazzy]

uh? I meant that was bad for file streams not taking a std::string as argument

[blackcoder41]

i see.

[Albatross]

They could have had an #ifdef #define #endif clause for adding string support to std::fstream.

It's neat to have separate libraries, but it's even neater to have libraries that work purfectly with each other, no?

-Albatross

[Bazzy]

They are both part of the standard library, not of separate libraries

[blackcoder41]

+1 Bazzy

[Albatross]

Chris:

No, I don't. std::fstream and std::string are separate libraries. A const char* is native, so it doesn't require a library to handle. That way, the libraries aren't inter-dependant.

Bazzy:

They are both part of the standard library, not of separate libraries

Well... I see you and chrisname need to have chat about that.

And I stand by my "it's even neater to have libraries that work purfectly with each other, no?"

-Albatross