Re: Luxasm news



Johannes Kroll <j-krollNO-SPAM-BLAH-BLAH@xxxxxx> écrivait news:d5dio9$8jp
$1@xxxxxxxxxxxxxxxxxx:

> On 05 May 2005 15:35:12 GMT
> Betov <betov@xxxxxxx> wrote:
>
>> Johannes Kroll <j-krollNO-SPAM-BLAH-BLAH@xxxxxx> écrivait
>> news:d5d8it$98h$1@xxxxxxxxxxxxxxxxxx:
>>
>> > You mean if RosAsm crashes the error must be in the user's source
>> > code?
>>
>> No. I mean that, once a tool is considered "pretty
>> stable", whatever that means, when the whole thingie
>> hangs, this is much probably not with a trivial and
>> standard Source, and that, in most case, this will
>> be because of some weird and unregular use of something
>> in the users's Source.
>>
>> The fact that such events help at pointing out real
>> bugs, in the programming tool is not the problem, and
>> is another story. The real problem is that, when
>> implementing out-of-reason securities for the user
>> typings, you put the user's source in danger, because
>> the worst enemy of a source is the programmer himself,
>> and certainaly not the Tool he is using.
>
> I get what you say but the last sentence is really strange. Somehow you
> seem to be "educating" the users to believe "If RosAsm crashes I must
> have done something wrong"...

Does not the experience show that we tend to most often
suspect the Tools, the OS, or anything, more easily than
our own actions?

To make a perenthesis out of the "RosAsm case", let us
consider what happends when "we Hang the OS" with our
developements. In that case, there is no doubt that the
OS _should not hang_ and this simply shows a week point
that we can call a OS bug. There is no doubt, also, that
we are educated - hopefull - to conclude that we also did
"something wrong".

Now, for a Programming Tool like RosAsm, having "touchable
Developpers", Board, and all, the users do not hezitate
to report the occasional hangs, even if they could be
pushed to think "I must have done something wrong"...


Betov.

< http://rosasm.org >



.



Relevant Pages

  • Re: Evolution
    ... >> Errors Management is a per cases based implementation providing ... >> don't recall the last time i had some report of that kind... ... Software that explodes, hangs, loops or dies silently is simply ... In hang case (hang of the RosAsm itself), ...
    (alt.lang.asm)
  • Re: Luxasm news
    ... > You mean if RosAsm crashes the error must be in the user's source code? ... to disk before the hangs shut-down. ... when the result of these faults might push the Tool ... as long as the bug, inside the programming Tool, will not be ...
    (alt.lang.asm)
  • Re: ASM vs HLL : absurd war
    ... Maybe a window and the basics of the drawing ... RosAsm Auto-Compile under ReactOS very last version. ... To try to point out more exactely at what point it hangs. ...
    (alt.lang.asm)
  • Re: [Attn: Randy] COM calling...
    ... > hangs. ... with an IQ around 80: RosAsm ... > errors cases management covers only the errors i am able to ... > imagine, ...
    (alt.lang.asm)
  • Re: Yet Another RosAsm Symbol table problem
    ... polite and sincere kind of guys, and he stay allways to facts and remain ... > prove to the amaized people that RosAsm is slower ... > to apply them to HLA2 WaporeWare, and to claim that, ... > and that, therefore, a programming Tool will, now on, ...
    (alt.lang.asm)