prefered way for support legacy C API on char* and std::string

[Olaf]

Hi,

I wrap a legacy C library, e.g. the signature is

void set_error_buffe r(char* buf);

where the buf length should be of length of 512 (it's defined).

Now I want to wrap it with std::string. What is the prefered way?

Thanks,
Olaf

[Victor Bazarov]

Olaf wrote:

I wrap a legacy C library, e.g. the signature is

void set_error_buffe r(char* buf);

where the buf length should be of length of 512 (it's defined).

Now I want to wrap it with std::string. What is the prefered way?

What do you expect to accomplish with 'std::string'? Apparently,
the API you're using is going to store the pointer to that buffer
and fill it in at some point in the future, without even asking
you about it. You simply cannot rely on them to be doing the same
thing to a 'std::string' object.

Of course, you could try defining a global 'std::string' object,
making sure it has at least 512 bytes and then passing the pointer
returned from its 'data()' member to that 'set_error_buff er', but
it's a BAD IDEA(tm). What I'd probably do:

class ErrorBufferWrap per {
char* buffer;
ErrorBufferWrap per(const ErrorBufferWrap per&);
ErrorBufferWrap per& operator=(const ErrorBufferWrap per&);
public:
ErrorBufferWrap per() : buffer(new char[512]) {
set_error_buffe r(buffer);
}
~ErrorBufferWra pper() { delete[] buffer; }
std::string asString() const { return std::string(buf fer); }
} const globalErrorBuff er; // notice the 'const'

...
// somewhere in your code
if (thereWasAnErro r)
std::cerr << globalErrorBuff er.asString() << std::endl;
...

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Kai-Uwe Bux]

Olaf wrote:

Hi,

I wrap a legacy C library, e.g. the signature is

void set_error_buffe r(char* buf);

where the buf length should be of length of 512 (it's defined).

Now I want to wrap it with std::string. What is the prefered way?

What does set_error_buffe r() do to the buffer? Does it just read it and use
the info found to set some internal error_state (in this case, the
signature could/should use char const *)? Or does it write some internal
error information into buf?

In the first case, you can do something like:

void set_error_buffe r( std::string const & str ) {
assert ( str.size() < 512 );
set_error_buffe r( str.c_str() );
}

This makes str.size() < 512 part of the contract and it would be the clients
responsibility to make sure the condition is not violated. If that is not
what you want, you could throw an exception or truncate the string
internally.
In the other case, you could do

void set_error_buffe r ( std::string & str ) {
char my_buffer [512];
set_error_buffe r( &my_buffer );
str.assign( &my_buffer );
}

This assumes(!) that set_error_buffe r will leave a 0-terminated string
whereever it writes.
Best

Kai-Uwe Bux

[Olaf]

What does set_error_buffe r() do to the buffer? Does it just read it and use

the info found to set some internal error_state (in this case, the
signature could/should use char const *)? Or does it write some internal
error information into buf?

It write internals into.

In the first case, you can do something like:

void set_error_buffe r( std::string const & str ) {
assert ( str.size() < 512 );
set_error_buffe r( str.c_str() );
}

This was my first attempt; the function wants to write into the buffer
and c_str() returns a const reference.

void set_error_buffe r ( std::string & str ) {
char my_buffer [512];
set_error_buffe r( &my_buffer );
str.assign( &my_buffer );
}

This assumes(!) that set_error_buffe r will leave a 0-terminated string
whereever it writes.

Yep,

Thanks,
Olaf

[Jim Langston]

"Olaf" <ol**@mdcc.dewr ote in message news:f7******** **@viper.mdlink .de...

Hi,

I wrap a legacy C library, e.g. the signature is

void set_error_buffe r(char* buf);

where the buf length should be of length of 512 (it's defined).

Now I want to wrap it with std::string. What is the prefered way?

Unfortunately, you don't have access to std::string's internal data.
However, you do have access to a std::vector's internal data.

I've toyed with using a std::vector instead of char array, but usually in my
classes I wind up using a char array anyway for this type of thing.
However, if the c-style function is reading from the data isntead of writing
to it, then I'll use std::string with .c_str()

[Rolf Magnus]

Olaf wrote:

>What does set_error_buffe r() do to the buffer? Does it just read it and
use the info found to set some internal error_state (in this case, the
signature could/should use char const *)? Or does it write some internal
error information into buf?

It write internals into.

>In the first case, you can do something like:

void set_error_buffe r( std::string const & str ) {
assert ( str.size() < 512 );
set_error_buffe r( str.c_str() );
}

This was my first attempt; the function wants to write into the buffer
and c_str() returns a const reference.

It returns a pointer to const char, and it does that for a reason. The
returned buffer must not be written to. There is no safe way to make a C
function directly write into an std::string.