Bug 262 – Missing DDoc comments in on Socket.blocking

Both the getter and the setter for the blocking property of Socket are missing DDoc comments. When reading the documentation, this makes it seem as if there is no way to configure a socket in blocking/non-blocking mode.

Something like this? /// The socket's blocking flag. /// When a socket is blocking, calls to receive(), accept(), and send() will block and wait for data/action. /// A non-blocking socket will immediately return instead of blocking. bool blocking() // getter /// ditto void blocking(bool byes) // setter Too much, or not enough information? Thanks, -[Unknown] > [email protected] wrote: >> Both the getter and the setter for the blocking property of Socket are >> missing >> DDoc comments. When reading the documentation, this makes it seem as >> if there >> is no way to configure a socket in blocking/non-blocking mode. > > > I know nothing about sockets. Can you provide some comments I can just > paste in?

It looks like when Ddoc comments were added, the blocking documentation was added to the wrong element (_blocking (Windows only) instead of blocking() (there are 2 for get/set, one needs a ditto)). There also seems to be other missing ddoc comments, such as SocketSet.max (which should be documented in the old doc), and a few constructors (e.g. the exceptions) do not show what the parameters are (simple /// by them should be enough). On Sun, 23 Jul 2006 15:41:12 -0400, Unknown W. Brackets <[email protected]> wrote: > Something like this? > > /// The socket's blocking flag. > /// When a socket is blocking, calls to receive(), accept(), and send() > will block and wait for data/action. > /// A non-blocking socket will immediately return instead of blocking. > bool blocking() // getter > > /// ditto > void blocking(bool byes) // setter > > Too much, or not enough information? > > Thanks, > -[Unknown] > > >> [email protected] wrote: >>> Both the getter and the setter for the blocking property of Socket are >>> missing >>> DDoc comments. When reading the documentation, this makes it seem as >>> if there >>> is no way to configure a socket in blocking/non-blocking mode. >> I know nothing about sockets. Can you provide some comments I can >> just paste in?

Fixed DMD 0.164 (added suggested documentation)