It appears that you're running an Ad-Blocker. This site is monetized by Advertising and by ">User Donations; we ask that if you find this site helpful that you whitelist us in your Ad-Blocker, or make a ">Donation to help aid in operating costs.

Now now some hostility. Yet what §in_tax just said is the truth of the matter. Well it will take time to learn, well another is approach is to ask her about it, that's the normal way of things lol. Yet this is moving away from *nix now anyway... Well that sig may have a point but that's one side of it.

Its not the same but it is close, and yes, you do have to be good at writing portable code. I know that it does handle c++ iofiles differntly. I just recently expierenced an instance of this when i was trying to use the ifstream command. It worked wonderfully on my nix box but when i tryed to transfer it over, it bombed. At any rate, i have no reall point to this post so.... yeah, just watch your code and you'll be fine

I'm a mostly client/server programmer. Are you SURE it's the same code for either platform? (provided you include the proper libraries, and don't use MS specific functions)

Cause I'm under the impression that working with sockets for windows is quite different from *nix. For instance, the root and core of my socket programming is having a callback function - which is the message queue for a WINDOW - to notify me of socket-related events.

If you write it in Java it's exactly the same code. I don't know about C, but I do know that the libraries you have to include are different. But since Java is on the VM it doesn't matter, and the code will work across all platforms. Even socket stuff.