how is string::c_str() implemented?

[Jess]

Hello,

I'm doing an exercise that defines a new abstract class "Str" that has
the same functions as "string" class, which holds a vector of chars.
But since I'm also trying to define a "c_str()" function, which copies
the chars from the vector into an array and return the pointer, I
think I need add another char array to my "Str" class. Now, the
problem is the size of the array has to be known in advance, but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

Thanks,
Jess

[Gianni Mariani]

Jess wrote:

Hello,

I'm doing an exercise that defines a new abstract class "Str" that has
the same functions as "string" class, which holds a vector of chars.
But since I'm also trying to define a "c_str()" function, which copies
the chars from the vector into an array and return the pointer, I
think I need add another char array to my "Str" class. Now, the
problem is the size of the array has to be known in advance, but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

c_str() simply needs to ensure that the character at one beyond the end
of the string contains a null. (i.e. '\000').

One way is to always allocate one more char than is needed and when
c_str() is called, plonk a nul at the end and return a pointer to your
internal buffer. This is probably the simplest solution.

Other solutions involve creating an auxiliary buffer as you noted.

[Rolf Magnus]

Jess wrote:

Hello,

I'm doing an exercise that defines a new abstract class "Str" that has
the same functions as "string" class, which holds a vector of chars.
But since I'm also trying to define a "c_str()" function, which copies
the chars from the vector into an array and return the pointer, I
think I need add another char array to my "Str" class.

If you already have it as a vector of char, there is no need to copy it.

Now, the problem is the size of the array has to be known in advance, but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

You could use a dynamically allocated array.

[Jess]

On May 6, 9:29 pm, Gianni Mariani <[e-mail]:

c_str() simply needs to ensure that the character at one beyond the end
of the string contains a null. (i.e. '\000').

One way is to always allocate one more char than is needed and when
c_str() is called, plonk a nul at the end and return a pointer to your
internal buffer. This is probably the simplest solution.

My internal buffer isn't an array, so perhaps I can't return a pointer
to it?

Other solutions involve creating an auxiliary buffer as you noted.

To create an auxiliary buffer, then I think I need to have a member
that is a char*, because I can't create a static array (since I don't
know its size in advance)...

Thanks,
Jess

[Jess]

On May 6, 9:38 pm, Rolf Magnus <[e-mail]:

If you already have it as a vector of char, there is no need to copy it.

Since c_str() returns an array of chars, do you mean I need to convert
the vector into an array?

>

Now, the problem is the size of the array has to be known in advance, but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

You could use a dynamically allocated array.

Is there a way to keep a dynamically allocated array as a member of a
class? I guess it's impossible. Then I think I can keep a char* as a
member and let it point to a dynamically allocated array (after I do
"new char[...]"). Is this the correct approach?

Thanks,
Jess

[=?iso-8859-1?q?Erik_Wikstr=F6m?=]

On 7 Maj, 08:55, Jess <[e-mail]:

On May 6, 9:38 pm, Rolf Magnus <[e-mail]:

If you already have it as a vector of char, there is no need to copy it.

Since c_str() returns an array of chars, do you mean I need to convert
the vector into an array?

Yes, a special property of std::vector is that all the elements are
guaranteed to be stored in contiguous memory (this means that all(?)
implementations of vector uses an array to store the elements. This
means that if you have a vector vec, then &vec[0] will give you a
pointer to the first element of the array used to store the elements.

So all you have to do is to make sure that you always keep an 0-char
at the end of the vector used to store your string in and then c_str()
will be as simple as 'return &vec[0];'. However remember that you have
the 0-char when you perform certain operations such as append so that
you don't add the new text after it.

Now, the problem is the size of the array has to be known in advance,but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

You could use a dynamically allocated array.

Is there a way to keep a dynamically allocated array as a member of a
class? I guess it's impossible. Then I think I can keep a char* as a
member and let it point to a dynamically allocated array (after I do
"new char[...]"). Is this the correct approach?

Yes, you can have a char* as a member and each time the string changes
you delete[] the old one and new[] a new char array. However as
described above this is not necessary, nor is it a good solution since
it would mean that you kept two instances of the string, on in the
vector and one in the char*.

--
Erik Wikström

[Sylvester Hesp]

"Erik Wikström" <er****@student.chalmers.sewrote in message
news:11**********************@w5g2000hsg.googlegro ups.com...

On 7 Maj, 08:55, Jess <[e-mail]:

On May 6, 9:38 pm, Rolf Magnus <[e-mail]:

If you already have it as a vector of char, there is no need to copy
it.

Since c_str() returns an array of chars, do you mean I need to convert

the vector into an array?

Yes, a special property of std::vector is that all the elements are
guaranteed to be stored in contiguous memory (this means that all(?)
implementations of vector uses an array to store the elements. This
means that if you have a vector vec, then &vec[0] will give you a
pointer to the first element of the array used to store the elements.

The horrendous vector<boolof course being the sole exception to this rule.
;)

- Sylvester

[Jess]

Thanks!

Jess

On May 7, 5:23 pm, Erik Wikström <[e-mail]:

On 7 Maj, 08:55, Jess <[e-mail]:

On May 6, 9:38 pm, Rolf Magnus <[e-mail]:

If you already have it as a vector of char, there is no need to copy it.

Since c_str() returns an array of chars, do you mean I need to convert
the vector into an array?

Yes, a special property of std::vector is that all the elements are
guaranteed to be stored in contiguous memory (this means that all(?)
implementations of vector uses an array to store the elements. This
means that if you have a vector vec, then &vec[0] will give you a
pointer to the first element of the array used to store the elements.

So all you have to do is to make sure that you always keep an 0-char
at the end of the vector used to store your string in and then c_str()
will be as simple as 'return &vec[0];'. However remember that you have
the 0-char when you perform certain operations such as append so that
you don't add the new text after it.

Now, the problem is the size of the array has to be known in advance, but
obviously, the array's size changes when the corresponding
vector<charchanges. Any suggestions on how I should implement the
c_str() function?

You could use a dynamically allocated array.

Is there a way to keep a dynamically allocated array as a member of a
class? I guess it's impossible. Then I think I can keep a char* as a
member and let it point to a dynamically allocated array (after I do
"new char[...]"). Is this the correct approach?

Yes, you can have a char* as a member and each time the string changes
you delete[] the old one and new[] a new char array. However as
described above this is not necessary, nor is it a good solution since
it would mean that you kept two instances of the string, on in the
vector and one in the char*.

--
Erik Wikström

[Default User]

Jess wrote:

Thanks!

Please don't top-post. Your replies belong following or interspersed
with properly trimmed quotes. See the majority of other posts in the
newsgroup, or the group FAQ list:
<http://www.parashift.com/c++-faq-lite/how-to-post.html>