Comments on: Available socket bytes http://www.dholm.com/2008/05/13/available-socket-bytes/ The trouble with programmers is that you can never tell what a programmer is doing until it's too late. Fri, 11 Feb 2011 06:28:05 +0000 hourly 1 http://wordpress.org/?v= By: dholm http://www.dholm.com/2008/05/13/available-socket-bytes/comment-page-1/#comment-101 dholm Mon, 26 May 2008 06:43:56 +0000 http://www.dholm.com/?p=67#comment-101 Long time, no see! Thanks for the suggestions! I fixed the implementation, apparently I don't have the ioctl_list man page. ;) Long time, no see!
Thanks for the suggestions! I fixed the implementation, apparently I don’t have the ioctl_list man page. ;)

]]> By: Martin http://www.dholm.com/2008/05/13/available-socket-bytes/comment-page-1/#comment-100 Martin Sat, 24 May 2008 20:43:20 +0000 http://www.dholm.com/?p=67#comment-100 Hi btw! :) Hi btw! :)

]]> By: Martin http://www.dholm.com/2008/05/13/available-socket-bytes/comment-page-1/#comment-99 Martin Sat, 24 May 2008 20:39:32 +0000 http://www.dholm.com/?p=67#comment-99 Also, since you're returning -1 to indicate an error I think you want ssize_t. That is, if I remember correctly (take e.g. ssize_t read(...) vs size_t fread(...)). Also, since you’re returning -1 to indicate an error I think you want ssize_t. That is, if I remember correctly (take e.g. ssize_t read(…) vs size_t fread(…)).

]]> By: Martin http://www.dholm.com/2008/05/13/available-socket-bytes/comment-page-1/#comment-98 Martin Sat, 24 May 2008 20:32:03 +0000 http://www.dholm.com/?p=67#comment-98 Eeek! man ioctl_list: "0x0000541B FIONREAD int *" That you might be lucky and it happens to work on your platform is no excuse. ;) Eeek! man ioctl_list:

“0x0000541B FIONREAD int *”

That you might be lucky and it happens to work on your platform is no excuse. ;)

]]>