The message scan_f_illegal_char seems to have gained additional parameters since it was

introduced. Take that into account to avoid an access violation.

git-svn-id: trunk@22749 -
This commit is contained in:
svenbarth 2012-10-18 20:12:28 +00:00
parent 2ada9a528b
commit ca6ca31953

View File

@ -221,6 +221,7 @@ const
var
token: tasmtoken;
forcelabel: boolean;
s : string;
begin
forcelabel := FALSE;
actasmpattern :='';
@ -504,7 +505,8 @@ const
end;
else
begin
Message(scan_f_illegal_char);
s:=c;
Message2(scan_f_illegal_char,s,'$'+hexstr(ord(c),2));
end;
end; { end case }