std::vector::as sign

[scooter]

what happens memory wise with this scenerio:

std::vector<int > vecInt(20, 999);

VecInt.assign(2 0, 0);
do all the 999 values get overwritten or does the vector reassign the
memory lso?

thanks

[Buster Copley]

scooter wrote:

what happens memory wise with this scenerio:

std::vector<int > vecInt(20, 999);

VecInt.assign(2 0, 0);
You have the parameters backwards.
do all the 999 values get overwritten or does the vector reassign the
memory lso?

Do you want the memory to be freed and reallocated?
If so, I know that

std::vector <int> vecInt (999, 20);

{
std::vector <int> temp ();
temp.swap (vecInt)
}

will do it. IIRC, vector::assign works identically to
constructing a new vector and using operator=, and in
that case (again IIRC) the memory is not guaranteed to
be released and reallocated.

Regards,
Buster.

[Buster Copley]

Buster Copley wrote:

scooter wrote:

what happens memory wise with this scenerio:

std::vector<int > vecInt(20, 999);

VecInt.assign(2 0, 0);

You have the parameters backwards.

I'm sorry, I misunderstood the next sentence. You're fine.

do all the 999 values get overwritten or does the vector reassign the
memory lso?

I think the 999s get overwritten.
Regards,
Buster.

[tom_usenet]

On Wed, 17 Sep 2003 20:18:39 +0100, Buster Copley <bu****@none.co m>
wrote:

scooter wrote:

what happens memory wise with this scenerio:

std::vector<int > vecInt(20, 999);

VecInt.assign(2 0, 0);
You have the parameters backwards.

do all the 999 values get overwritten or does the vector reassign the
memory lso?

Do you want the memory to be freed and reallocated?
If so, I know that

std::vector <int> vecInt (999, 20);

{
std::vector <int> temp ();

The above declares a function called temp, which isn't what you
wanted.
temp.swap (vecInt)
}

The canonical way to do this (which very few people seem to get right
for some reason), is:

std::vector<int >().swap(vecInt );

Tom

[Buster]

"tom_usenet " <to********@hot mail.com> wrote>

Do you want the memory to be freed and reallocated?
If so, I know that

std::vector <int> vecInt (999, 20);

{
std::vector <int> temp ();

The above declares a function called temp, which isn't what you
wanted.

Yes, silly of me. Thanks.

temp.swap (vecInt)
}

The canonical way to do this (which very few people seem to get right
for some reason), is:

std::vector<int >().swap(vecInt );

I have a question about that. I thought I read somewhere that a
temporary is not modifiable. Isn't the result of the expression
'std::vector <int> ()' (when it is an expression...) a temporary?
So what am I missing?

Regards,
Buster.

[tom_usenet]

On Thu, 18 Sep 2003 14:53:41 +0100, "Buster" <no***@nowhere. com>
wrote:

I have a question about that. I thought I read somewhere that a
temporary is not modifiable. Isn't the result of the expression
'std::vector <int> ()' (when it is an expression...) a temporary?
So what am I missing?

Temporaries are modifiable, it's just that you can't bind them to
non-const references. e.g. this is illegal:

vecInt.swap(std ::vector<int>() );

Here a temporary is passed as the argument to swap. This argument is a
non-const reference, so the code is illegal.

So, to summarize, you can call member functions (const or non-const)
on non-const temporaries, but you can't bind them to non-const
references. This is why the standard swap technique works, but some
alternatives don't.

Tom