Irrlicht Engine

I wonder ... what's the advantage of irr::core::stringw , instead of std::wstring ? Why does irrlicht implements another wstring class ?

(I said it was a n00b question )

I presume its for portability. If people just use the Irrlicht provided types, etc then they have a standard to work with and don't need to worry about the underlying implementation.

irr::core:stringw could, for example on one system map directly to std::wstring but on another operating system or environment, std::wstring might not be available, so another implementation can be written, while maintaining the standard 'irr::core::stringw' interface for developers.

exactly, darkliquid