On Mon, 16 Feb 1998 14:40:21 -0500 (EST), Orlando Llanes wrote:
Another thing to note is that GPC will return the actual first and last element number, but BP starts it at 0 and ends on the last element. For example, if the index goes from -1 to 4, BP will treat it as 0..6 whereas GPC (and any Standard Pascal compliant Pascal Compiler?) will treat it as -1..4 (don'tcha just LOVE GPC?!?!?!?! :)
Um, so Low()/High() return the indices of the lower/upper bound of the array, right? [Just making sure I understood the examples, as I have no experience with these BP functions]
It seems to me that the GPC behavior makes more sense (and would return more useful values), or was that your point? What good does Low() do in BP if it always returns a 0?
-Kevin
-- Kevin A. Foss --- kfoss@mint.net
On Mon, 16 Feb 1998, Kevin A. Foss wrote:
Um, so Low()/High() return the indices of the lower/upper bound of the array, right? [Just making sure I understood the examples, as I have no experience with these BP functions]
Yes, High() and Low() return the upper and lower bound of the array (First()/Last() are defined in Delphi which I think work the same, haven't tried it lately).
It seems to me that the GPC behavior makes more sense (and would return more useful values), or was that your point? What good does Low() do in BP if it always returns a 0?
My point was showing how something BP specific can be translated to GPC.
By showing how BP treats the indices as compared to GPC, I was not comparing which is better, I was showing the differences in behavior seeing as to how they return different values.
The purpose of High()/Low()/Low..High is so that you can change the size and indices of the array and not have to hard code the values.
See ya! Orlando Llanes
"Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!"
"Look out fo' flyeeng feet" O__/ a010111t@bc.seflin.org /|____. O <__. /> / \ ____________|_________ http://ourworld.compuserve.com/homepages/Monkey414
-
Kevin A. Foss -
Orlando Llanes