I don't know if this bug is related to Lazarus, WebLaz or FPC. Please tell me and I'll post it on Mantis:

To reproduce it, please follow this steps:

1) Create a CGI application. You'll need WebLaz package.
2) Add an FPWebModule.
3) Add two or three actions. Compile and check if they work as expected.
4) Delete the method "onRequest..." of one action from code, DO NOT REMOVE THE ACTION USING THE ACTIONS EDITOR, just delete the method similar to this (from interface and implementation):

    procedure myActionRequest(Sender: TObject; ARequest: TRequest;
      AResponse: TResponse; var Handled: Boolean);

5) Compile and test. When you invoke any action of this webmodule, you'll get this:

Error reading XXXXXXX.Actions: Error reading TFPWebAction.OnRequest: Invalid value for property

procedure TForm1.Button1Click(Sender: TObject);
var
   iLastError: integer;
begin
   iLastError:=10053;
   if iLastError in [10053, 10054] then Label1.Caption:='Yes, it works!'
                                   else Label1.Caption:='No, it doesn''t
work!';
   // Output : No, it doesn''t work!
end;
procedure TForm1.Button2Click(Sender: TObject);
begin
   iLastError:=53;
   if iLastError in [53, 54] then Label1.Caption:='Yes, it works!'
                             else Label1.Caption:='No, it doesn''t work!';
   // Output : Yes, it works!
end;

Is there A compiler directive for testing on big nummers?

(fpc:2.6.1 Lazarus: 1.0.3 i386 on Windows 7 x64)

29.11.2012 2:15, Erwin van den Bosch ?????:

This should generate range check errors, because AFAIK sets are limited to byte values.

No.

(fpc:2.6.1 Lazarus: 1.0.3 i386 on Windows 7 x64)

I don't know if this bug is related to Lazarus, WebLaz or FPC. Please

tell me and I'll post it on Mantis:

To reproduce it, please follow this steps:

1) Create a CGI application. You'll need WebLaz package.
2) Add an FPWebModule.
3) Add two or three actions. Compile and check if they work as expected.
4) Delete the method "onRequest..." of one action from code, DO NOT REMOVE THE ACTION USING THE ACTIONS EDITOR, just delete the method similar to this (from interface and implementation):

    procedure myActionRequest(Sender: TObject; ARequest: TRequest;
      AResponse: TResponse; var Handled: Boolean);

5) Compile and test. When you invoke any action of this webmodule, you'll get this:

Error reading XXXXXXX.Actions: Error reading TFPWebAction.OnRequest: Invalid value for property

That's normal, as if you delete a generated event handler from any application (e.g. OnClick of a TButton). The resource file is not automatically updated with your changes in the code. Simply don't do such a thing, and use the actions editor, that's why it exists.

You may be thinking of how "in" is used in a for..in..do loop like this

procedure TForm1.Button1Click(Sender: TObject);
var
    iLastError, j: integer;
    intArray: array[0..1] of integer = (10053,10054);
begin
    iLastError:=10053;
    for j in intArray do
     if j=iLastError
      then begin
            Label1.Caption:='iLastError present';
            Break;
           end
     else label1.Caption:= 'iLastError not found';
end;

I should have turned range checking on! Then I saved a few hours debugging :-(

Thanks for your answer.

Well, I wouldn't try to synchronize code with lfm, but I'd add more info to the error message, for example "...Invalid value for property AAAAA", just add the property with problems.

for example "...Invalid value for property AAAAA"

AAAAA in

Error reading TFPWebAction.OnRequest: Invalid

is TFPWebAction.OnRequest

Ok, OnRequest is the property. Then, it could help if the message is changed to:

Invalid value (name_of_removed_method) for property TFPWebAction.OnRequest.

Feel free to file a feature request