«

Hi Group,

sorry for my for you surely dumb question. But i'm not so familiar with this
reference- and pointerstew in C++ yet.

Let me explain my problem with a little Codesnippet.

If i do the following:

void CServerSock::OnAccept(void)
{
CSocket clientsock;

.... // some irrelevant code here
this->Accept(clientsock);
.... // some irrelevant code here
}

all went fine. The function Accept is a Member of CServerSock and documented
as

void Accept(CSocket &)

I understand it this way, that the Accept-Function takes a Reference to a
CSocket-Object, right? But there is a problem for me. The Documentation for
CSocket says further:

"If the Object goes out of scope, the connection is automatically
closed"

So, as the Object in my a.m. example is created on the stack, it goes out of
scope immediately when the OnAccept()-Function ends. And than the connection
is closed (what i don't want to happen now!)

The documentation for Accept says:

"The referenced Object can be created on the stack or on the heap"

Yeah! That's it! I thought! I have to create my socket-object on the heap
instead. So i tried sth. like that:

void CServerSock::OnAccept(void)
{
CSocket *clientsock = new CSocket();

.... // some irrelevant code here
this->Accept(clientsock);
.... // some irrelevant code here
}

But now the compiler complains with:

"Cannot convert from class CSocket * to class CAsyncSocket &"

(CSocket is derived from CAsyncSocket - so it should work, isn't it?)
So the problem must be, that a csocket* (Pointer) is sth. different from
csocket& (Reference). I read many pages on the net which states that a
Reference is a const pointer to sth. a.s.o. but i never discovered the
general idea and the background.

Tried a lot versions with

- CSocket const *clientsock
- const CSocket *clientsock
- and, and, and, ...

Nothing worked. Sometimes other errors in the compiler occured, often the
same again and again. Sometimes no error occured and i was able to compile.
But then, at runtime, i get a programcrash for the not right reference to
the object.

So my question is:
How can i get (How must i note to get) a Reference to a memory block/Object
that was created on the heap with the new operator. How can i get a & to an
object when i only have a * to it? How can i keep the compiler happy?

I take the syntax alone, but i really will be happy if there are 1 or 2
sentences of explanation why it should be so or so and not the other way. Is
there a simple explanation how i have to imagine a Reference or a Pointer
(the difference) so i am able to understand it and solve my future problems
with such things on my own (i like more to learn than only to solve sth.).

Any good (understandable for such a lamer like me) webpages out there?

Thx. in advance! Your help, hints, urls, explanations, solutions, money
)), best wishes )) are really appreciated!
CU
Joerg Toellner

On Mon, 14 Jul 2003 10:19:13 +0200, "JoTo" <> wrote:

>void CServerSock::OnAccept(void)
>{
> CSocket *clientsock = new CSocket();
>
> .... // some irrelevant code here
> this->Accept(clientsock);
> .... // some irrelevant code here
>}
>
>But now the compiler complains with:
>
> "Cannot convert from class CSocket * to class CAsyncSocket &"
>

You have a pointer, the argument must be an object, to get an object
(the thing pointed to) from a pointer do


Accept( *clientsock );


But you have a more severe problem, that the CSocket object is never
deallocated.

One possibility could be to make this object a member of CServerSock.

Hello Alf and Group,

"Alf P. Steinbach" <> schrieb im Newsbeitrag
news:...
> >void CServerSock::OnAccept(void)
> >{
> > CSocket *clientsock = new CSocket();
> >
> > .... // some irrelevant code here
> > this->Accept(clientsock);
> > .... // some irrelevant code here
> >}
> >But now the compiler complains with:
> > "Cannot convert from class CSocket * to class CAsyncSocket &"
> You have a pointer, the argument must be an object, to get an object
> (the thing pointed to) from a pointer do
> Accept( *clientsock );

Hmmm! I thought i tried this variant already with the same result (compile
error). But maybe i only think i have done THIS variant in the mess i've
done with "fishing in the dark" . So i try it again and will see.

> But you have a more severe problem, that the CSocket object is never
> deallocated.
> One possibility could be to make this object a member of CServerSock.

Thx for the hint. I have already a member variable

CSocket *myclient[3];

in my Application-Object where i store the pointer in the OnAccept function
(in the irrelevant code sections) with

myapp->myclient[x] = clientsock;

(where x is 0|1|2 in case which clientsock is "free" at the moment)
And of course i'll do a

delete(myapp->myclient[x]);

later (on end of connection, end of app, a.s.o.). Is this enough for what
you suggest?

I need more than one clientsocks (there should be 3 connections at the same
time possible) and use the clientsock later for sending msgs to the
connected participants (thats why i must create it on the heap).

I hope this is what you meant with your "deallocate"-hint. If not please
explain further if possible what i need to do.

But let me first thank you very much for your fast reply. I'll try it and
cross my fingers with hope. ) Sometimes C++ is like black magic and vodoo
for me. But I'll get it ......... sometimes! ))

CU and Thx.
Joerg Toellner

Thanks Andrew,

i'll try it when i'm at home this evening. I hope the compiler has the same
opinion like you and all the others here. )))

Thx. all for you patience.
Where is the desk where i have to pay the bill now? )

Yours
Joerg Toellner

"Andrew Koenig" <> schrieb im Newsbeitrag
news:...
> Let me summarize the problem.
> You write
> CSocket clientsock;
> this -> Accept(clientsock);
> and it works just fine except for the fact that clientsock is a
> local variable and is therefore destroyed at the wrong time.
> So you want to create the object on the heap instead.
> Here's how to do that:
> CSocket* socket_ptr = new CSocket;
> this -> Accept(*socket_ptr);
> And then, when you're done with the object, delete it:
> delete socket_ptr;