Related articles |
---|
[14 earlier articles] |
Re: Generating Java Bytecode kuznetso@MIT.EDU (1996-11-21) |
Re: Generating Java Bytecode billms@ee.ucla.edu (Bill Mangione-Smith) (1996-11-21) |
Re: Generating Java Bytecode pardo@cs.washington.edu (1996-11-21) |
Re: Generating Java Bytecode lynch@frigg.cci.de (Andrew Lynch) (1996-11-24) |
Re: Generating Java Bytecode am56@dial.pipex.com (Stefan Heinzmann) (1996-11-24) |
Re: Generating Java Bytecode guerby@gnat.com (1996-11-26) |
Re: Generating Java Bytecode gvreugde@uwaterloo.ca (1996-11-26) |
Re: Generating Java Bytecode jaidi@ubd.edu.bn (Nor Jaidi) (1996-11-26) |
Re: Generating Java Bytecode Freek.Wiedijk@phil.ruu.nl (1996-12-01) |
Re: Generating Java Bytecode jsa@alexandria.organon.com (1996-12-01) |
Re: Generating Java Bytecode jgreene@inmet.com (Jeremy Greene) (1996-12-01) |
Re: Generating Java Bytecode Antoine.Leca@renault.fr (Antoine Leca) (1996-12-01) |
Re: Generating Java Bytecode kaleja@rahul.net (Russell Bornsch++) (1996-12-03) |
[1 later articles] |
From: | gvreugde@uwaterloo.ca (Gord Vreugdenhil) |
Newsgroups: | comp.compilers |
Date: | 26 Nov 1996 20:24:24 -0500 |
Organization: | University of Waterloo |
References: | 96-11-108 96-11-125 96-11-132 |
Keywords: | Java, Ada |
Joe Hummel <jhummel@crispix.ICS.UCI.EDU> writes:
> Ada doesn't support general pointers, ...
> I would imagine that Ada does support something like:
>
> p = (void *) 0x0080001F;
>
> so I don't know how they get around this. Perhaps they don't support
> it? Anyone know?
Not quite the same thing, but you can say things like:
for p use at 16#0080001F#;
which physically places the variable "p" at location 16#0080001F#.
Since the address is an expression, you could use this to build
the above. Ada does require that the "at" expressions do not
overlap with either a name or another "at"; ie. the "at" cannot
create an alias. (ARM '83, 13.5)
Gord.
--
Gord Vreugdenhil Comp. Sci. Dept., Davis Centre, U. of Waterloo
gvreugde@plg.uwaterloo.ca Waterloo, ON N2L 3G1
(519) 888-4567 ext. 4452 Fax: (519) 885-1208
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.