From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bertrand.Jeannet@inria.fr>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 406F17EE99
	for <caml-list@sympa.inria.fr>; Wed, 11 Dec 2013 12:46:07 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.93,871,1378850400"; 
   d="scan'208";a="40455194"
Received: from wificampus-092101.grenet.fr (HELO [130.190.92.101]) ([130.190.92.101])
  by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 11 Dec 2013 12:46:06 +0100
Message-ID: <52A8508D.2050000@inria.fr>
Date: Wed, 11 Dec 2013 12:46:21 +0100
From: Bertrand Jeannet <Bertrand.Jeannet@inria.fr>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: caml-list@inria.fr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Caml-list] Mismatch between Gc.full_major() documentation and
 behaviour

According to the documentation, the sequence 
"Gc.major();Gc.full_major()" should be equivalent to "Gc.full_major()", 
as Gc.full_major() is told to terminate the current major gc and perform 
a complete new cycle.

In my case it is not the case: "Gc.major(); Gc.full_major()" performs 
more calls to finalisation functions than "Gc.full_major()".

My context: I use a weak hashtables containing finalised value (with 
Gc.finalise).

The documentation of Weak module specifies that the finalization 
function is called after the weak hashtbl/array has been set to none.

Does someone know the explanation of this ?