hex converting

[David Crow]

You don't need this at all. Dangleberry's post was just showing you how to convert a number to a string (which was then displayed in a message box).

[NewHSKid]

For the send command, i have problems it needs the socket and a message and a length, and some flags. Its says I can't use int because the message has to be const char *. for the length is that in bytes? should it be 4 or 10 to represent all numbers/letters? Jimmy Just cause I am 15, doesn't mean I'm dumb! (I'll really be 4 on Feb. 29...the year 2004)

[David Crow]

How about a code snippet of what you are trying to do?

[NewHSKid]

hi, here is what i want to do, the program is connected to the server already. (I don't know how to connect, i just use my friends dad program to connect) int message; message = 0x5FF0023A; send(s, message, strlen(message), 0); It says send can't convert parameter 2 from int to const char * and it says the same thing about strlen. Jimmy Just cause I am 15, doesn't mean I'm dumb! (I'll really be 4 on Feb. 29...the year 2004)

[David Crow]

NewHSKid wrote: the program is connected to the server already. (I don't know how to connect, i just use my friends dad program to connect) Does that mean he is supplying you with a valid socket descriptor? Given that the second parameter of send() is expecting a char*, you'll need:

int nMessage = 0x5FF0023A;
char szMessage[9]; // hold 8 characters plus a \0
sprintf(szMessage, "%d", nMessage); // or itoa(nMessage, szMessage, 16);
int nBytes = send(s, szMessage, lstrlen(szMessage), 0);

[NewHSKid]

Hi, Thanks for helping. So when i use that code, the receiving program will get the hex number of 5FF0023A? Jimmy Just cause I am 15, doesn't mean I'm dumb! (I'll really be 4 on Feb. 29...the year 2004)

[Lost User]

try this : send(s, (const char FAR*)message, sizeof(message), 0); though the sizeof(message) param can just be 0, as message oriented sockets will send a zero-length transport datagram. :cool:

[David Crow]

No, the recv() function on the other end will receive "5FF0023A" as a char*. It can convert that to an integer (long actually) with strtol(). long lMessage; char szMessage[9], *stop; int nBytes = recv(s, szMessage, sizeof(szMessage), 0); lMessage = strtol(szMessage, &stop, 16);

[Ken Mazaika]

Windows Sockets can be highly complicated as well as windows programming for people somewhat new to programming. From your posts it seems as if your skipping quite a few steps in the learning process. I think if you ended up writing a program that does what you want now it will be mostly cut/paste code and you won't get much out of the experience. This program would be an excellent learning experience, but you should make creating it more of a long range goal.

[Terry ONolley]

The only actual "numbers" in the computer are semi-conductor gates that are either on or off. That is fine for the computer, but most people need something visual to help us understand what is going on. To the computer, all numbering base sytems look the same - binary. It is only when outputting the graphical representation of those numbers that you need to worry about data types and base. So, the number 255 is represented in the coputer by 8 logic gates being on: 11111111 If you, the human, wants to see that number in hexadecimal, then you tell your program to format that number in base 16 and you see "FF". Now, the characters "FF" are represented by the ascii code for the letter 'F' - which is 70 or x40 - so if you looked at the raw bits for the characters "FF" you would see 70 70 or the bits 01000110, 01000110. So what happened??? You started with 11111111 and ended up with 01000110, 01000110! The confusion comes from figuring out what format the reciever of the data is expecting. That is what function headers are for. They define how to interperet the bits that are being sent.

---

---