<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 4: ncSetSocketNonBlocking</title><link>https://sourceforge.net/p/netclass/bugs/4/</link><description>Recent changes to 4: ncSetSocketNonBlocking</description><atom:link href="https://sourceforge.net/p/netclass/bugs/4/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 28 Jun 2010 11:12:16 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/netclass/bugs/4/feed.rss" rel="self" type="application/rss+xml"/><item><title>ncSetSocketNonBlocking</title><link>https://sourceforge.net/p/netclass/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This macro causes an access violation error under windows, wxDevCpp with debugging enabled.&lt;/p&gt;
&lt;p&gt;#define ncSetSocketNonBlocking(a) ioctlsocket(a,FIONBIO,(unsigned long *)0x01)&lt;/p&gt;
&lt;p&gt;I think it's because the last argument is a pointer and winsock attempts to write something in it. As a quick fix I use&lt;/p&gt;
&lt;p&gt;unsigned long arg = 0x01;&lt;br /&gt;
ioctlsocket(m_sockfd,FIONBIO,&amp;amp;arg);&lt;/p&gt;
&lt;p&gt;But it's still kinda annoying, thought you should know.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Toster</dc:creator><pubDate>Mon, 28 Jun 2010 11:12:16 -0000</pubDate><guid>https://sourceforge.net1872347c7a9b16cfab8d7bb5f11996335561a995</guid></item></channel></rss>