[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-commits-nodiffs] Revision c59614b8cbac8b49ff6be02a88245fd3ad41
From: |
monotone |
Subject: |
[Monotone-commits-nodiffs] Revision c59614b8cbac8b49ff6be02a88245fd3ad410720 |
Date: |
Mon, 25 Aug 2008 00:41:18 +0200 |
-----------------------------------------------------------------
Revision: c59614b8cbac8b49ff6be02a88245fd3ad410720
Ancestor: 1d7e91951e2040c8d7f87a37cbf76d2bb844c01d
Author: address@hidden
Date: 2008-08-24T22:16:23
Branch: net.venge.monotone.contrib.lib.automate-stdio
Modified files:
Monotone/AutomateStdio.pm
ChangeLog:
- Make sure that the destructor does not throw any exceptions and does not reset
any exception status that may be present when it is called.
- Make sure that the closedown() method does not allow its use of the eval
statement to reset any currentl exception status.
Bit of a nasty bug this one! Basically because the object was blessed before the
exception was raised in the constructor, Perl immediately calls the destructor,
which in turn calls code that uses eval, thereby resetting $@ and loosing the
details of the original exception.
monotone --db={your.database} diff
--revision=1d7e91951e2040c8d7f87a37cbf76d2bb844c01d
--revision=c59614b8cbac8b49ff6be02a88245fd3ad410720
----------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-commits-nodiffs] Revision c59614b8cbac8b49ff6be02a88245fd3ad410720,
monotone <=