Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: A cast pointer is NOT an lvalue!? (ANSI C)
Keywords: X3J11, pointers, cast, lvalue
Message-ID: <14005@mimsy.UUCP>
Date: 15 Oct 88 15:07:55 GMT
References: <479@midgard.mn.org> <8663@smoke.ARPA> <482@midgard.mn.org>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 12

In article <482@midgard.mn.org> dal@midgard.mn.org (Dale Schumacher) asks:
>... If an implementation stores different object types in different
>areas of memory, then wouldn't that fail also?  How would one implement
>malloc() on such a machine?

The short answer is `one would not'.  The long one is that maybe it
would work if the compiler recognised allocation calls (malloc, calloc)
and inserted special typing information.  At any rate, this sort of
thing is why `new' is a keyword in other languages.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris