Go to file
velter 9dd1dd0111 Compiler bug in const arrays
There a compiler bug in array constants. A construct like

procedure B(eType : TObject);
begin
	if eType is TObject then ;
end;

function A(eVal : int32) : booleen;
begin
	result:=not(eVal in [1,2]);
end;         

begin
	A(1);
	A(2);
	A(3);
end;


Cause an AV in UpsCompiler line 6185. The root cause is the use of FindAndAddType with no name. The function return the last created anonymous type. In the previous sample it's a Type created by the "is" operator which is not an array. Casting it to TPSArrayType lead to the AV.
2014-05-27 14:51:17 +02:00
Addon XE6 support was added 2014-04-16 13:09:14 +03:00
Articles articles were added 2012-06-26 15:35:33 +03:00
dunit re-checkin 2006-05-30 14:23:25 +00:00
help re-checkin 2006-05-30 14:23:25 +00:00
Samples 46955: PascalScript: Warning shows wrong row,col number in some constructions 2012-02-17 09:30:56 +00:00
Source Compiler bug in const arrays 2014-05-27 14:51:17 +02:00
unit-importing Patches for the unit importer by Alexander Federyakov. 2010-12-08 12:19:49 +00:00
.gitignore Add a .gitignore for *.dcu 2013-01-12 15:50:53 +01:00
Pascal Script.ico re-checkin 2006-05-30 14:23:25 +00:00
patch.exe re-checkin 2006-05-30 14:23:25 +00:00