From: dennison@telepath.com
Subject: Re: Big-endian vs little-endian
Date: 1999/02/08
Date: 1999-02-08T00:00:00+00:00 [thread overview]
Message-ID: <79n1h0$4r1$1@nnrp1.dejanews.com> (raw)
In-Reply-To: 36BD02DB.737849EE@hso.link.com
In article <36BD02DB.737849EE@hso.link.com>,
"Samuel T. Harris" <sam_harris@hso.link.com> wrote:
> also a security concern). Since then, I have always advocated
> producing width, image, and value functions for all important
> data types. In fact, I have generics which produce these functions
> for arrays (trivial) and records (almost trivial) so the overhead
> for developing these functions is insignificant. An they do come
> in handy when a little text_io based debugging instrumentation
> is needed. A simple put_line(image(whatever)); is always available.
Cool idea! But what method do you use to make generation of records "almost
trivial"? And how do you handle pointers?
T.E.D.
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
next prev parent reply other threads:[~1999-02-08 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-29 0:00 Big-endian vs little-endian Mike Werner
1999-02-02 0:00 ` Nick Roberts
1999-02-03 0:00 ` Mark A Biggar
1999-02-06 0:00 ` Samuel T. Harris
1999-02-08 0:00 ` dennison [this message]
1999-02-08 0:00 ` Samuel T. Harris
1999-02-04 0:00 ` Richard D Riehle
1999-02-06 0:00 ` Mike Werner
1999-02-07 0:00 ` Matthew Heaney
1999-02-09 0:00 ` Stephen Leake
1999-02-10 0:00 ` Mike Werner
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox