In article <I4ednTtV75vq23HbnZ2dnUVZ_jednZ2d@comcast.com>,
Thomas Dineen <tjjdineen@comcast.net> writes:
> Gentle People:
>
> I have found an interesting Endinness issue.
>
> On both Solaris 8 Sparc and Solaris 8 IA32
> machines when I read the same file sequentially
> using getc() and I get different results in byte
> ordering because of the Big Endian (Sparc) versus
> Little Endian (Intel) file system data organization.

If you read the same file sequentially using getc(),
you won't see any difference due to endianism.
Endianism only comes into play when you are dealing
with multiple byte quantities, but getc() only gives
you a byte at a time, and behaves identically on
little and big endian systems.

> Question is there any way to automatically
> compensate for this with getc??? Or more obviously
> do I just have to rewrite the software application
> to compensate for this?

You'll have to describe more accurately what the
problem is.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]