Age | Commit message (Collapse) | Author | |
---|---|---|---|
2009-01-19 | This should fix the problem of never knowing if your sockets are closed. Now | Mike Buland | |
Bu::Socket::read will throw an exception if the socket has been closed. Also, you'll get an exception at object creation if the socket could connect to a computer, but not the given port. | |||
2009-01-16 | I...think that's a little better. Wow, function pointers in windows have a | Mike Buland | |
lot of problems. This may require a little more research, but basically, you can't just call them inline wherever you'd like. I managed to get it to work by providing simple one line wrapper functions for each function we acquired as a pointer. Crazy mess. Anyway, it should load the library just once now, and Bu::Socket looks a little bit cleaner, but not a heck of a lot. I also added some more docs and removed the author references. |