Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalThis is not the only method missing from the standard library, it was intended be low level. This use case and many other are covered by general libraries such as:
QtCore & QString has my preference: it supports UTF8 and uses less templates, which means understandable errors and faster compilation. It uses the "q" prefix which makes namespaces unnecessary and simplifies headers.
Boost often generates hideous error messages and slow compile time.
POCO seems to be a reasonable compromise.
This is not the only method missing from the standard library, it was intended be low level. This use case and many other are covered by general libraries such as:
QtCore & QString has my preference: it supports UTF8 and uses less templates, which means understandable errors and faster compilation.
Boost often generates hideous error messages.
POCO seems to be a reasonable compromise.
This is not the only method missing from the standard library, it was intended be low level. This use case and many other are covered by general libraries such as:
QtCore & QString has my preference: it supports UTF8 and uses less templates, which means understandable errors and faster compilation. It uses the "q" prefix which makes namespaces unnecessary and simplifies headers.
Boost often generates hideous error messages and slow compile time.
POCO seems to be a reasonable compromise.
This is not the only method missing from the standard library, it was intended be low level. This use case and many other are covered by general libraries such as:
QtCore & QString has my preference: it supports UTF8 and uses less templates, which means understandable errors and faster compilation.
Boost often generates hideous error messages.
POCO seems to be a reasonable compromise.
