Paolo Carlini <[EMAIL PROTECTED]> writes:
| Paolo Carlini wrote:
|
| >I think something is going wrong with types characterized by
| >""non-trivial"" constructors, e.g., doing memory allocation from the heap.
| >
| >Gaby can you look into this?
| >
| >
| Gaby, I see __valarray_copy used (instea
Paolo Carlini <[EMAIL PROTECTED]> writes:
| Jhair Tocancipa Triana wrote:
|
| >Please consider the program below (backtrace included (gcc 4.0.2
| >(Ubuntu))). The program crashes when doing a std::slice on a valarray
| >containing a structure with a string element in it.
| >
| >
| Just wanted t
Jhair Tocancipa Triana <[EMAIL PROTECTED]> writes:
[...]
| I am not sure why *__b is a 0x0-string, and who should be responsible
| to initialize it correctly (__b is initialized in the C++ library). It
| is mandated by the standard that only POD types are allowed in a
| valarray?
The reason is b
Paolo Carlini wrote:
>I think something is going wrong with types characterized by
>""non-trivial"" constructors, e.g., doing memory allocation from the heap.
>
>Gaby can you look into this?
>
>
Gaby, I see __valarray_copy used (instead of __valarray_copy_construct)
by the conversion constructor
Jhair Tocancipa Triana wrote:
>Please consider the program below (backtrace included (gcc 4.0.2
>(Ubuntu))). The program crashes when doing a std::slice on a valarray
>containing a structure with a string element in it.
>
>
Just wanted to say that this has nothing to do with string specifically,
Please consider the program below (backtrace included (gcc 4.0.2
(Ubuntu))). The program crashes when doing a std::slice on a valarray
containing a structure with a string element in it.
Is what I am doing there undefined behaviour? I've read 26.3.4 from
the standard but got no clues.
As you can
