On Tue, 30 Oct 2012, Cody Permann wrote:
Actually now that I think about it, those strings come out of the
Exodus API as char arrays anyway. We convert them to strings after
the fact.
This solution really isn't that bad especially since we
can just leave them in their native formats long enough
to distribute.
It's definitely a decent hack.
And actually, there don't seem to be any non-hackish ways to do fancy
Parallel:: stuff with std::basic_string. Unless I misread the C++
standard, it's not safe to try to write into a c_str() or data()
derived pointer even if the string is large enough to hold what you
intend to write, so the current Parallel:: operations on strings have
to receive into temporary vector buffers before copying the result
into strings anyway.
I guess the C++ standard designers are trying to give standard library
implementors enough latitude to do rope-data-structure, copy-on-write,
etc. designs if they want?
---
Roy
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
