Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Library : Other (not classified elsewhere) » Segfaults with One container?
Re: Segfaults with One container? [message #23183 is a reply to message #23180] Thu, 24 September 2009 10:22 Go to previous messageGo to previous message
phirox is currently offline  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)
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Dockmenu Draw
Next Topic: How to set a global (system) keyboard hook?
Goto Forum:
  


Current Time: Tue May 14 14:28:19 CEST 2024

Total time taken to generate the page: 0.02964 seconds