Apologies if this comes through as a repeat.

What is so mysterious/non-responsive about telling you (read the initial email) 
that I was re-writing an existing file, nothing happened, no errors were 
reported, and that repeating it with an explicit truncation of the file after 
opening gave the expected behavior?

What I find ironic about your objections is that *my* problem is long-since 
fixed.  I was asking a question the answer to which might have shed some light 
on how to construct an example that would be useful in analyzing what happened. 
 In short, I was trying to help you and others.  Sorry, I don't see how giving 
me "talking Elisa" in response to that is in any way helpful or justified.

Examples are good, but the system has to be trustworthy to run in unknown 
situations.  Robust error reporting is critical to that goal.  Sadly Squeak has 
a long tradition of silent failure and a culture that thinks it is perfectly 
ok.  I find it dangerous.

Bill



________________________________________
From: [email protected] 
[[email protected]] On Behalf Of [email protected] 
[[email protected]]
Sent: Sunday, November 14, 2010 10:44 PM
To: [email protected]
Subject: Re: [Pharo-project]    Unix thing? Possible silent failure     writing 
file.

Wilhelm,

This comment, which we know is coming from a SW developer, looks like an 
automatic "Elisa" like IA bot replying syntactically correct English but not 
adding exchange in the dialogue.

Your description of the unexpected (for you, that is) behavior doesn't allow us 
to understand minimally if the 'failure' is:

a) a mismatch between your expectation and actual, albeit correct behavior;
b) an intermittent occurrence or a systematic one, i.e., reproducible one;
c) _what_ exactly was you doing in your code and in which context.

Also, since you mentioned Windows to Unix transition, is the 'silent' failure 
in Unix 'not silent' if you run the same code?

I hope that by now you can understand why we need a minimum piece of code in 
order to envision the tackling of an "ultimately fix".

Regards,

--
Cesar Rabak




Em 14/11/2010 19:26, Schwab,Wilhelm K < [email protected] > escreveu:
If that's how you want it.  My concern is not over the failure; it's over its 
silence.  I fear that saying nothing only reduces our collective opportunity to 
ultimately fix it.



________________________________________
From: [email protected] 
[[email protected]] On Behalf Of Stéphane Ducasse 
[[email protected]]
Sent: Sunday, November 14, 2010 4:21 PM
To: [email protected]
Subject: Re: [Pharo-project] Unix thing? Possible silent failure        writing 
file.

send a code snippet else it does not help to send the mail.


On Nov 14, 2010, at 10:19 PM, Schwab,Wilhelm K wrote:

> Surely I'm not the only person to make the Windows to Unix move.  It is 
> either something that happens, or another case of the Squeak primitives 
> failing without saying that they did, let alone why.  What you call a crystal 
> ball, I call words from the wise who might have seen something similar before.
>
>
>
>
> ________________________________________
> From: [email protected] 
> [[email protected]] On Behalf Of [email protected] 
> [[email protected]]
> Sent: Sunday, November 14, 2010 3:43 PM
> To: [email protected]
> Subject: Re: [Pharo-project] Unix thing? Possible silent failure writing      
>   file.
>
> Without a minimum snippet of the code that purportedly got into this 
> incident, only a crystal ball can help here. . .
>
>






Reply via email to