Path: utzoo!news-server.csri.toronto.edu!rutgers!gatech!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Portability vs. Endianness
Message-ID: <15469@smoke.brl.mil>
Date: 13 Mar 91 21:38:26 GMT
References: <2628@ksr.com> <15457@smoke.brl.mil> <2669@ksr.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <2669@ksr.com> jfw@ksr.com (John F. Woods) writes:
>Further hmm.  Is memcpy() obliged to do anything sensible if handed
>a pointer to an integer cast to a void *?

Yes, memcpy() can be used to copy any valid object.

By the way, I think I have a correct solution for the original problem
embedded as a subset of what the MUVES Dx package does when sending
data between heterogeneous architectures, but it is hard to extract
from the context.