Consider the following program:

{$mode objfpc}
uses sysutils;
begin
  try
    try
      raise exception.create('test');
    except
      on e: exception do begin
        e.message := 'tset';
        raise e; // correct re-raise should only have raise; no exception
variable may present
      end;
    end;
  except
    writeln('oow');
  end;
end.

which is a wrong way to re-raise an exception. The program runs but after the outer exception handler ('oow'), it ends with EAccessViolation. Is this the intended behavior?

I tested in Delphi XE, it also crashes. So, yes it is intended behaviour.

It is not desirable, of course. But there is no way the compiler can decide whether the 'raise e' statement is correct.

Michael.

That's bad to know :|
What if you ask Embarcadero first? Probably they missed the point. I don't have Delphi so I can't ask them.

Like I said, there is no way of knowing what is correct or not.

I don't really see what can be done except maybe checking if an object is already in the exception stack before adding it again (which I assume is what is happening)

Michael.