U++ framework: U++ Library : Other (not classified elsewhere)

Home » U++ Library support » U++ Library : Other (not classified elsewhere) » Segfaults with One container?

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: Segfaults with One container? [message #23183 is a reply to message #23180]

Thu, 24 September 2009 10:22

phirox
Messages: 49
Registered: December 2007

Member

luzr wrote on Thu, 24 September 2009 09:43

I am not quite happy about this; I think Socket::Data should in fact be private. I guess Socket::Attach(SOCKET) would solve the problem, right?

Such a function would be great, but would need one addition. Socket settings such as linger/blocking/delay will not be saved in the class specific variables, even though they will remain effective on the socket itself. I can find only one that is really used; to determine if to peek or directly read. So the function should at least be Socket::Attach(SOCKET, is_blocking)

Report message to a moderator

[Message index]

		Segfaults with One container? By: phirox on Tue, 22 September 2009 13:21
		Re: Segfaults with One container? By: mirek on Tue, 22 September 2009 17:52
		Re: Segfaults with One container? By: phirox on Wed, 23 September 2009 09:22
		Re: Segfaults with One container? By: mirek on Thu, 24 September 2009 09:43
		Re: Segfaults with One container? By: phirox on Thu, 24 September 2009 10:22
		Re: Segfaults with One container? By: mirek on Thu, 24 September 2009 11:06
		Re: Segfaults with One container? By: phirox on Thu, 24 September 2009 12:25
		Re: Segfaults with One container? By: mirek on Fri, 02 October 2009 10:01

Previous Topic:	Dockmenu Draw
Next Topic:	How to set a global (system) keyboard hook?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Sep 17 01:00:06 GMT+2 2026

Total time taken to generate the page: 0.00556 seconds