Xref: utzoo comp.lang.misc:1319 comp.lang.c:8522
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.lang.misc,comp.lang.c
Subject: Re: HLLs vs asm (was Re: portable "asm")
Message-ID: <7876@oberon.USC.EDU>
Date: 25 Mar 88 08:23:02 GMT
References: <11702@brl-adm.ARPA> <243@eagle_snax.UUCP> <2245@geac.UUCP> <1592@ogcvax.UUCP> <l.712> <1600@ogcvax.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Followup-To: comp.lang.misc
Organization: USC AIS, Los Angeles
Lines: 22

In article <1600@ogcvax.UUCP> pase@ogcvax.UUCP (Douglas M. Pase) writes:
>``C'' allows you to
>ignore types when you really want to,

The only way it allows you do do this is via unions, equivelent to
pascal's varient records.  Casts are (by definition) conversions,
while some seem silly and produce no code on many machines, they still
never allow you to "ignore types".  Pointers DO NOT violate this,
while it is possible to cast any pointer to a void or char pointer and
back, it is not required that the char pointer be meaningful.  (Ever
heard of "split I & D"?  How about extending this so char and int
storage are seperate?)

> plus it allows access to the "bare
>metal", etc.)

Are we talking about the same language?
-- 
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%fns1@ecla.usc.edu
			oberon!fns1!info-prime-request