From: <do...@ni...> - 2000-05-09 16:12:47
|
Sam Steingold >>>> In message <14616.8287.153168.570162@ragged> >>>> On the subject of "Re: clisp socket interface small request" >>>> Sent on Tue May 09 09:29:07 EDT 2000 >>>> Honorable Don Cohen <do...@ni...> writes: >> Sam Steingold >> there are issues of "host order" vs "network order". >> >> What are these issues? What are host and network order? see byteorder(3n) - ntohl, ntohs, htonl, htons This sounds like endianness stuff. I don't think it's relevant, especially if you treat the networdk address as a single integer. I want the addresses from the same "class {A,B,C} network to share the same {8,16,24} MOST significant bits. I'm pretty sure this is what everyone else would also want. >> since you don't need the number anyway (what are you gonna do with it, >> print with ~:d? :-) and all functions which take it, also take the >> >> No, I'm going to do things like compare two of them to find out >> whether they have the same first n bits in common - if n is a >> multiple of 8 I could do a string compare, but that still seems >> crazy. so you want a bitvector (byte vector?) you will have to wait for Bruno to express his opinion on this. Ok, I imagine by now he understands what I'm asking for. |