On Jun 9, 2008, at 9:58 PM, Russell Leighton wrote: > > On Jun 9, 2008, at 8:52 PM, Igor Tandetnik wrote: > >> "Alex Katebi" <[EMAIL PROTECTED]> >> wrote in message >> news:[EMAIL PROTECTED] >>> I am trying to implement remote procedure calls (RPC) for SQLite API >>> to be used in my application. >>> In particular sqlite3_column_double( ) returns a floating point >>> double. How can I write this double value into a TCP socket? >> >> How do you write an int, or a string, into a socket? A double >> wouldn't >> be much different: at the end of the day, it's just an 8-byte buffer. >> > > Aren' t there aligment and endian issues as well as potential floating > point representations between platforms? >
Endianness might be a problem, though these days it is becoming increasingly difficult to find a big-endian processor. I don't think different floating point representations are an issue since I am not aware of any modern machine that does anything other than IEEE754. SQLite assumes IEEE754 floating point representation, so if you have a machine that uses something different, SQLite won't work on it (or at least it won't have a compatible file format.) I have never yet heard of this being a problem for anyone. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
