From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA11909; Wed, 2 Oct 2002 17:54:18 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA12226 for ; Wed, 2 Oct 2002 17:54:17 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from athlon.baretta.com (r-mi214-6a241.tin.it [62.211.4.241]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id g92FsG504825 for ; Wed, 2 Oct 2002 17:54:16 +0200 (MET DST) Received: from baretta.com (localhost.localdomain [127.0.0.1]) by athlon.baretta.com (Postfix) with ESMTP id DF5E32739E; Wed, 2 Oct 2002 18:04:10 +0200 (CEST) Message-ID: <3D9B18FA.80809@baretta.com> Date: Wed, 02 Oct 2002 18:04:10 +0200 From: Alessandro Baretta Organization: Baretta srl -- www.baretta.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: it, en MIME-Version: 1.0 To: "Yaron M. Minsky" , Ocaml Subject: Re: [Caml-list] Uncaught exceptions (or am I going crazy?) References: <3D9B03DF.5040806@cs.cornell.edu> <3D9B0978.E4A5D96@beaune.inria.fr> <3D9B1306.6050208@cs.cornell.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk Yaron M. Minsky wrote: > All the explanations given so far make sense except for one thing: they > all suggest that the program should terminate. But my program doesn't > terminate, it just prints out the "Uncaught exception" string and keeps > on executing. I am not to my knowledge making any use of threads, so > that odesn't seem like it should be the right explanation either. > > So, any more thoughts? > > y I noticed this. You are probably linking to a library which raises and then catches the exception, printing out the error message. Oftentimes, GUI libraries have this feature. This might explain why your program does not terminate when the exception is raised. Can you send in a test case that reproduces this behavior, for reference? Alex ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners