Experimental Physics and
Industrial Control System

Kay-Uwe Kasemir <[email protected]> · Wed, 02 Mar 2005 15:13:54 -0500

On Mar 2, 2005, at 14:30, Jeff Hill wrote:

There isnt anything fundamentaly wrong with the streambuf
interface other than its complexity.

Hi:

My gut feeling is that it's so complicated
that it _must_ be fundamentally wrong.
Besides, even if I could understand it:
Can I actually use my own allocator & "char_traits"
on more than one compiler for more than one year?

Back to strings, memory in fixed chunks, and CA:
In order to have a client and server exchange
huge strings or custom data types, is it acceptable
to require a compatible configuration of memory chunk
sizes?

So is it unthinkable to restrict yourself to a
memory chunk size that - on vxWorks or RTEMS - will be configured
on startup and your strings have to fit in there?
So EPICS strings won't be limited to e.g. 40 chars.
On swapping operating systems they are even 'virtually unlimited',
and on e.g. vxWorks you can only serve strings that fit within
one memory chunk?

That way they don't need to be split across memory blocks,
and their interface can be C-style to which
every C++ class library (which of course comes with its custom
string class) can interface.

-Kay

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System