Delphi 4 fixes and known issues

Delphi
Documentation
Support

Additional Resources
Technology Partners
Books
Community

DELPHI DEVELOPER SUPPORT

Delphi 4 fixes and known issues

BASM SECTION

Areas of concentration under: basm

errors and warnings

Area: basm\errors and warnings

Reference Number: 546 (Published: 11/12/98)

Status: Deferred to Next Rel
Date Reported: 5/22/98

Severity: Commonly Encountered

Type: Minor Functionality Failure

Problem:
Error message when using an Int64 as a for loop control variable states that it must be an ordinal value. this should be special cased and mention it has to be a *32-bit* ordinal value, since Int64 is ordinal.

Area: basm\errors and warnings

Reference Number: 960 (Published: 12/18/98)

Status: Deferred to Next Rel
Date Reported: 7/11/98

Severity: Commonly Encountered

Type: Unknown

Problem:
Inappropriate error message. I wrote something similar to the code in Steps. X needed to be a 64 bit integer. In the past I declared X as a COMP. Now I've changed it to INT64. And the compiler told me that there was an illegal type used in the writeln. -- I was flabergasted. I thought that maybe the WRITELN statement hadn't been updated to allow INT64. I was spinning around for a little while before it occured to me that I used the X:#:# format which was correct for COMP because it is officially floating point. I needed to use the X:# instead which is correct for any other type. The error message was misleading and had me running in circles.

NOTE: These listings are for informational use only. It is not intended for use when calling Borland's Developer Support Department.
If you have any suggestions or complaints about these 'Delphi Enhancements and Fixes' pages, please contact the Delphi Administrator. This e-mail address is not intended for support issues.

Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved.
Report Piracy, Legal Notices, Privacy Policy

Last Modified Thursday, 22-Mar-2001 18:57:04 EST


Delphi Documentation Support Additional Resources Technology Partners Books Community		DELPHI DEVELOPER SUPPORT Delphi 4 fixes and known issues BASM SECTION Areas of concentration under: basm errors and warnings Area: basm\errors and warnings Reference Number: 546 (Published: 11/12/98) Status: Deferred to Next Rel Date Reported: 5/22/98 Severity: Commonly Encountered Type: Minor Functionality Failure Problem: Error message when using an Int64 as a for loop control variable states that it must be an ordinal value. this should be special cased and mention it has to be a 32-bit ordinal value, since Int64 is ordinal. Area: basm\errors and warnings Reference Number: 960 (Published: 12/18/98) Status: Deferred to Next Rel Date Reported: 7/11/98 Severity: Commonly Encountered Type: Unknown Problem: Inappropriate error message. I wrote something similar to the code in Steps. X needed to be a 64 bit integer. In the past I declared X as a COMP. Now I've changed it to INT64. And the compiler told me that there was an illegal type used in the writeln. -- I was flabergasted. I thought that maybe the WRITELN statement hadn't been updated to allow INT64. I was spinning around for a little while before it occured to me that I used the X:#:# format which was correct for COMP because it is officially floating point. I needed to use the X:# instead which is correct for any other type. The error message was misleading and had me running in circles. NOTE: These listings are for informational use only. It is not intended for use when calling Borland's Developer Support Department. If you have any suggestions or complaints about these 'Delphi Enhancements and Fixes' pages, please contact the Delphi Administrator. This e-mail address is not intended for support issues.