Path: utzoo!attcan!uunet!lll-winken!ames!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: malloc impossible?
Message-ID: <9384@smoke.BRL.MIL>
Date: 15 Jan 89 16:32:11 GMT
References: <19@xenlink.UUCP> <225800106@uxe.cso.uiuc.edu> <310@twwells.uucp> <15427@mimsy.UUCP> <1010@vsi.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <1010@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes:
>> One can imagine a machine with different spaces for each different
>> intrinstic data type, where malloc() has to select from one of 8
>> or 16 possibilities.  Of course, since malloc() gets only one argument,
>> it has no way to decide which address space to use.
>Wow. Wouldn't structs be *really* interesting on a machine like this?

Don't worry, unless all those spaces are "shadowed", C cannot be
implemented on it.

X3J11 was very careful to ensure that memcpy() could be implemented
portably in ANSI C in the obvious way.

The talk about different kinds of data spaces is thus a red herring.