Re: FastMM 4.13 Exceptions
- From: "Peter Morris [Droopy eyes software]" <pete@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 15 Jul 2005 12:15:57 +0100
> My point is that it is not possible for a range check error to occur in
> the following code:
>
> ...
> for i := 0 to high(SmallBlockTypes) do
> begin
> if not Assigned(SmallBlockTypes[i].UpsizeMoveProcedure) then
Maybe you should use Low(SmallBlockTypes) instead of 0?
Isn't there a compiler directive to start arrays at 1 instead of 0? I can't
remember.
--
Pete
====
ECO Modeler, Audio compression components, DIB graphics controls,
FastStrings
http://www.droopyeyes.com
Read or write articles on just about anything
http://www.HowToDoThings.com
My blog
http://blogs.slcdug.org/petermorris/
.
- Follow-Ups:
- Re: FastMM 4.13 Exceptions
- From: Pierre le Riche
- Re: FastMM 4.13 Exceptions
- From: Robert Marquardt
- Re: FastMM 4.13 Exceptions
- References:
- FastMM 4.13 Exceptions
- From: Mark Gebauer
- Re: FastMM 4.13 Exceptions
- From: Pierre le Riche
- Re: FastMM 4.13 Exceptions
- From: Mark Gebauer
- Re: FastMM 4.13 Exceptions
- From: Pierre le Riche
- Re: FastMM 4.13 Exceptions
- From: Mark Gebauer
- Re: FastMM 4.13 Exceptions
- From: Pierre le Riche
- FastMM 4.13 Exceptions
- Prev by Date: Re: FastMM 4.13 Exceptions
- Next by Date: Re: FastMM 4.13 Exceptions
- Previous by thread: Re: FastMM 4.13 Exceptions
- Next by thread: Re: FastMM 4.13 Exceptions
- Index(es):
Relevant Pages
|
