From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Idea: Array Boundary Checks on Write Access Only
Date: 1998/06/20
Date: 1998-06-20T00:00:00+00:00 [thread overview]
Message-ID: <dewar.898364644@merv> (raw)
In-Reply-To: 6mb7jl$edm$1@nnrp1.dejanews.com
<<> It would then also be a nice option if the compiler would be
> able to dump a list of all the checks that it still had to insert
> to give developers a clue of whether they can by intelligently
> placing a manual check at the right place make a large number
> of automatically inserted less efficient checks unnecessary.
>>
In fact the RM requires (in annex H) that a fuloly conforming compiler
have some way of informing you of runtime time checks that are inserted.
next prev parent reply other threads:[~1998-06-20 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-15 0:00 Idea: Array Boundary Checks on Write Access Only Markus Kuhn
1998-06-15 0:00 ` Peter Amey
1998-06-20 0:00 ` Robert Dewar
1998-06-21 0:00 ` Markus Kuhn
[not found] ` <dewar.898490510@merv>
1998-07-09 0:00 ` Frank Klemm
1998-06-17 0:00 ` Stephen Leake
1998-06-17 0:00 ` Markus Kuhn
1998-06-17 0:00 ` Robert A Duff
1998-06-18 0:00 ` Anonymous
1998-06-18 0:00 ` Stuart Palin
[not found] ` <6m8v02$r2l$1@xenon.inbe.net>
1998-06-18 0:00 ` Markus Kuhn
1998-06-18 0:00 ` Lieven Marchand
1998-06-20 0:00 ` Robert I. Eachus
1998-06-18 0:00 ` dennison
1998-06-20 0:00 ` Robert Dewar [this message]
1998-06-18 0:00 ` Stuart Palin
1998-06-18 0:00 ` dennison
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox