On 4/1/11, DaWorm wrote:
> On Fri, Apr 1, 2011 at 9:09 AM, Bart wrote:
> It
> seems to me like a lot of effort to trap something that will rarely
> happen.
But it does happen.
I don't mind that it raises an exception in Destroy (although I find
it rather odd), but the consequences of raising t
On Fri, Apr 1, 2011 at 9:09 AM, Bart wrote:
>> The test case was an invalid filename. Is this the primary failure
>> method?
>
> This was merely to demonstrate the possibility of the destructor failing.
What other things would make the destructor of the TIniFile fail? It
seems to me like a lot
On 4/1/11, DaWorm wrote:
> The test case was an invalid filename. Is this the primary failure
> method?
This was merely to demonstrate the possibility of the destructor failing.
Bart
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://l
On Fri, Apr 1, 2011 at 6:28 AM, José Mejuto wrote:
> An exception in free is an extreme rare condition, but it could
> happend, and is better that your software stops to work than notify 2
> years later that your 2 zillions of INI files were not written at all
> because the user write a non valid
Hello FPC-Pascal,
Friday, April 1, 2011, 9:58:24 AM, you wrote:
MVC> 2. Cache the updates, and make sure they are written when the instance is
destroyed.
MVC> This is the current behaviour. It works fast, but the corner case you
encountered
MVC> (an error when updating the file in the d
Hello FPC-Pascal,
Friday, April 1, 2011, 12:17:30 AM, you wrote:
B> The job of the destructor, however, is to clean up the object and return
memory.
B> This should never fail IMHO.
The clean up has not been successfully performed as in this class a
file update is part of the clean up. There are
