Contract violations aren't exceptions, they aren't supposed to be caught in a retry clause.

The require clause:

require
i <= 2

Doesn't mean an exception will be raised if i is greater than 2, it means you have a program bug that needs to be fixed because someone called find while i was bigger than 2.

Before you call `find' you should have a function that checks to make sure i <= 2 and take an appropriate measure if it is not.

Thank LeMahieu. I have fixed your code like this:

class
	EXCEPTION2
 
create
	make
 
feature {ANY}
 
	make
        do
        	io.put_string ("Entry make%N")
            one
            two
            io.put_string ("Exit make")
        end
 
    one
        -- Exception in 'proc' require clause is raised in *calling* function, 'one'
        local
            retried: BOOLEAN
            value: INTEGER
        do
            io.put_string ("you call one method%N")
            if not retried then
                value := proc (3)
            end
        rescue
        	io.put_string ("You call one's rescue%N")
            retried := True
            retry
        end -- one
 
    two
        -- Exception in 'proc' ensure clause is raised in *called* function, 'proc'
        local
            value: INTEGER
        do
        	io.put_string ("you call two method%N")
            value := proc (2)
        end -- two
 
    proc (i: INTEGER): INTEGER
        require
            i <= 2
        local
            retried: BOOLEAN
        do
            io.put_string ("you call proc method%N")
            if not retried then
                Result := 2 * i
            end
        ensure
            Result <= 3
        rescue
        	io.put_string ("You call proc's rescue%N")
            retried := True
            Result := 3
            retry
     end -- proc
 
end

And in the feature, cussor stop at instruction :

	i <= 2

I meant when I debug the screen view like I hope it would be. My question is: Why is there diffrent from two that way, when I use F5 to run, and when I use F10 to bug ? Any more, I know that use F5 to run file, when the violation or exception is occured the programme will stop and not excute any more, but I don't hope such that. How can I fix this? I mean in Java I can catch the exception and process it in proper way, and when I press F5 to run Java file, and when an exception occur and catch, the programme won't stop and continue excute. See this example: <java> public class Except {

   public Except(){
   	int a = 0;
   	System.out.println ("Enter construction method");
   	try{
   		System.out.println (1/a);
   	}
   	catch(Exception e){
   		System.out.println (e.toString ());
   	}
   	System.out.println ("Exit construction method");
   }
   public static void main(String[] args) {
   	new Except();
   }

} </java> And the out put screen is: <java> Enter construction method java.lang.ArithmeticException: / by zero Exit construction method

Process completed. </java> As you see "Exit construction method" is still viewed in the screen. In eiffel I don't see it. How can you explain this? Best wishes !