@Xsense, your idea sounds more along the lines of network theorems. "Its best to use a low-level library" is utter posh. You use what you have available, or use what you can make available. The worst thing you could ever do is communicate with the driver directly via its direct interfaces. That has to be the worst idea I've ever seen. Unless you absolutely know what your doing, never, ever directly send commands to the driver, and never, ever use a low-level interface that is a thin wrapper around the direct instructions to the network card. That's what high level libraries are for. Like .NET, for example. They abstract away the incredibly large lines of code you'd normally need to write to get something going. Its simply a very, very bad idea. Copy-pasting code is bad, I agree; but sometimes, it can be helpful. Most of the time its useless though. Also, you most likely *won't* learn much from using low-level network libraries at all; you'll most likely only be putting yourself through hell. If you were to walk up to a professional programmer or computer scientist and tell them this idea, they'd laugh in your face. Like I said, don't ever consider dropping to the really low APIs unless you're project has requirements so specific that you require such a level of control. Otherwise, don't even think about it.
-- Audiogames-reflector mailing list Audiogamesfirstname.lastname@example.org https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector