Re: compile error about void*

From:

=?Utf-8?B?R2Vvcmdl?= <George@discussions.microsoft.com>

Newsgroups:

microsoft.public.vc.language

Date:

Fri, 18 Jan 2008 01:34:00 -0800

Message-ID:

<ADFEDE0C-F143-41ED-99D3-097C76A3514C@microsoft.com>

Thanks Uli,

I have tested your code.

#include <memory>

using namespace std;

typedef int array[100];

int main()
{
std::auto_ptr<array> p(new array);

return 0;
}

I got errors,

1>d:\visual studio 2008\projects\test_void1\test_void1\main.cpp(9) : error
C2664: 'std::auto_ptr<_Ty>::auto_ptr(_Ty (*)) throw()' : cannot convert
parameter 1 from 'int *' to 'array (*)'
1> with
1> [
1> _Ty=array
1> ]
1> Types pointed to are unrelated; conversion requires
reinterpret_cast, C-style cast or function-style cast

You got the same errors?

regards,
George

"Ulrich Eckhardt" wrote:

Igor Tandetnik wrote:

Note that new (void*[100]) and new void*[100] are different. The former
allocates a single element of type void*[100], which must be deallocated
with delete. The latter allocates 100 elements of type void*, and must
be deallocated with delete[].

Igor, I think you are wrong here, even though I agree with your logic. I
can't exactly explain it, but I had a similar false assumption cleared by a
discussion on comp.lang.c++.moderated. My approach was roughly this:

typedef int array[100];
auto_ptr<array> p(new array);

IOW, I create a type alias for an array which then allows me to use
non-array new and non-array delete (via auto_ptr) to manage objects of that
type. What I was told is that new decides on the complete type whether it
is the array form or not.

I'll try to locate the thread over the weekend and post the update here.

Uli