![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Byte Padding | naan | High Level Programming | 6 | 02-22-2007 05:09 AM |
| AWK and padding values | kshelluser | UNIX for Dummies Questions & Answers | 3 | 11-29-2006 05:14 PM |
| Padding variables | flounder | High Level Programming | 1 | 09-05-2006 01:11 PM |
| Padding | vijaygopalsk | UNIX for Dummies Questions & Answers | 2 | 06-27-2003 11:51 AM |
| Zero Padding to a string | Wing m. Cheng | High Level Programming | 3 | 09-16-2002 10:58 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
If you are talking about stuff like this:
struct foo { int bar; char c; DEFIT honk; long snafu; }; ... struct foo *pfoo = malloc( ...); ... send_from_1_2_other(pfoo, ....); ... This is a bad idea. It will only work inside an absolutely heterogenous, eh, structure. You would want to either have a conversion routine in each end, like ntohfoo(), htonfoo() modelled after the int and long ones, or, depending on the contents, you might want to transfer in ASCII, taking performance issues into account. Atle |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|