"Simon Parker" <simonparkerulm@gmail.com> wrote in message news:l2rts2F4d20U12@mid.individual.net...

On 08/02/2024 09:51, billy bookcase wrote:

"Simon Parker" <simonparkerulm@gmail.com> wrote in message
news:l2hde1Ffnc3U52@mid.individual.net...

<snip>

But failing to anticipate and rectify such an *obvious* user *error*
- unless I'm mistaken and there is indeed some specific function
which *is* indeed activated by *repeated* use of the [enter] key -
is simple incompetence. With bells on

But that is not a software error. It is a system design error.

So just to be clear before proceeding any further can you give an example
of what you yourself would consider a "software error"

< remainder snipped again on the "one step at a time principle >

I'll use the Visual Basic MsgBox for this example as one doesn't need to be a software
developer to follow the code. If you'd prefer a different language, let me know and
I'll see what I can do.

<Begin Code>
Dim Msg, Style, Title, Help, Ctxt, Response, FormatAns
Msg = "Do you want to Format the Hard Drive?" ' Define Question
Style = vbYesNo Or vbCritical Or vbDefaultButton2 ' Define Buttons
Title = "Sample Software Error for Mr Bookcase" ' Define Box Title
Help = "BUGGY.HLP" ' Define Help file
Ctxt = 1000 ' Define Topic Context
' Display Message and Get Response
Response = MsgBox(Msg, Style, Title, Help, Ctxt)
If Response = vbYes Then ' User chose Yes
FormatAns = "Yes"
Else ' User chose No.
FormatAns = "Yes"
End If
<End Code>

Regardless of the button clicked, "FormatAns" is "Yes" and the drive is likely to be
reformatted.

I consider this a "software error". Do you concur?

Only if the user doesn't wish to format the hard drive.

Or doesn't like playing "Format Russian Roulette"

(Another "Deer Hunter" reference there BTW)

So nice try; but again no cigar

When you again could have saved yourself so much trouble

do{print "OOPS!"}
while(2+2<>5)

The "while" would more normally reference an external
conditional which could, as it eventually turns out,
never be satisfied.

Hint; to save yourself valuable time in the future, perhaps you should limit yourself
to just the one highly questionable assertion each post.

That creaking sound you can hear, if you listen very carefully, is the thin ice upon
which you are skating starting to break.

If only the reasoning matched the metaphors.


bb

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

"Simon Parker" <simonparkerulm@gmail.com> wrote in message news:l2urqjF4d1vU12@mid.individual.net...

On 11/02/2024 21:25, billy bookcase wrote:

"Simon Parker" <simonparkerulm@gmail.com> wrote in message
news:l2rts2F4d20U12@mid.individual.net...

On 08/02/2024 09:51, billy bookcase wrote:

So just to be clear before proceeding any further can you give an example >>>> of what you yourself would consider a "software error"

< remainder snipped again on the "one step at a time principle

I'll use the Visual Basic MsgBox for this example as one doesn't need to be a
software
developer to follow the code. If you'd prefer a different language, let me know and
I'll see what I can do.

<Begin Code>
Dim Msg, Style, Title, Help, Ctxt, Response, FormatAns
Msg = "Do you want to Format the Hard Drive?" ' Define Question
Style = vbYesNo Or vbCritical Or vbDefaultButton2 ' Define Buttons
Title = "Sample Software Error for Mr Bookcase" ' Define Box Title
Help = "BUGGY.HLP" ' Define Help file
Ctxt = 1000 ' Define Topic Context >>> ' Display Message and Get Response
Response = MsgBox(Msg, Style, Title, Help, Ctxt)
If Response = vbYes Then ' User chose Yes
FormatAns = "Yes"
Else ' User chose No.
FormatAns = "Yes"
End If
<End Code>

Regardless of the button clicked, "FormatAns" is "Yes" and the drive is likely to be
reformatted.

I consider this a "software error". Do you concur?

Only if the user doesn't wish to format the hard drive.

Do you consider the example provided above a "software error"? A narrative answer is
not required. A simple "Yes" or "No" will suffice.> <snip "Deer Hunter" reference>

So nice try; but again no cigar

Pardon? The question posed was: "can you give an example of what you yourself would
consider a 'software error'"

Are you saying that you do not consider the example provided demonstrates a software
error?

There is no way of knowing.

Because while you may have commented the actual code what is
conspicuoulky lacking is any explanation of that piece of code
is actually intended to achieve

Which in poroperly documented code would normally expected
at the start

As I've explained to you more than once now a softawre "fault" arises
when program or piece of code doesn't achieve the result which was
intended.

Thus looking at the code which you have submitted , in the absence
of any supporting documentation there are two possibilities

This code has been produced by someone with a clear grudge
against society, Someone with a desire to get even determined to
lure innocent people into unwittingly wiping their hard disks and
losing all their data. Maybe Apple users especially but that
would be optional

And so as such, quite possibly it could be very successful !

In achieveing its stated objectives.

No faults at all !

The question would then arises of course as to how a user could ever find themselves in a situation where they would need to choose an option "not"
to wipe their hard drive.

So might I suggest you first set up a website, "Formatting Your Hard Drive" giving all the possible benefits and the obvious disadvantages. And get
them to print it all out ! OS, all data and all programmes lost,
And then get them to wipe their drives after pressing [NO]

On the other hand, if that wasn't your actual intention in writing that code then I can only suggest you get another hobby,.

Or if you want real world examples Sainsburys Self Srervice tills are overloaded with them. Given their supposed purpose of speeding
customers through the process.

When you again could have saved yourself so much trouble

You didn't ask me to provide the simplest example of a software error I could muster,

you asked for an example which is what I gave you.

Except you didn't. See above

do{print "OOPS!"}
while(2+2<>5)

The "while" would more normally reference an external
conditional which could, as it eventually turns out,
never be satisfied.

I accept that you have provided an example of a software error.

Is a point to all this likely to appear on the horizon anytime soon?

Ah........ "Horizon"


bb

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

"Simon Parker" <simonparkerulm@gmail.com> wrote in message news:l313ofF4d20U22@mid.individual.net...

On 12/02/2024 22:19, billy bookcase wrote:

"Simon Parker" <simonparkerulm@gmail.com> wrote in message
news:l2urqjF4d1vU12@mid.individual.net...

On 11/02/2024 21:25, billy bookcase wrote:

"Simon Parker" <simonparkerulm@gmail.com> wrote in message
news:l2rts2F4d20U12@mid.individual.net...

On 08/02/2024 09:51, billy bookcase wrote:

So just to be clear before proceeding any further can you give an example
of what you yourself would consider a "software error"

< remainder snipped again on the "one step at a time
principle

New Spellchecked Version

>

I'll use the Visual Basic MsgBox for this example as one doesn't need to be a
software
developer to follow the code. If you'd prefer a different language, let me know
and
I'll see what I can do.

<Begin Code>
Dim Msg, Style, Title, Help, Ctxt, Response, FormatAns
Msg = "Do you want to Format the Hard Drive?" ' Define Question
Style = vbYesNo Or vbCritical Or vbDefaultButton2 ' Define Buttons
Title = "Sample Software Error for Mr Bookcase" ' Define Box Title >>>>> Help = "BUGGY.HLP" ' Define Help file >>>>> Ctxt = 1000 ' Define Topic Context >>>>> ' Display Message and Get Response
Response = MsgBox(Msg, Style, Title, Help, Ctxt)
If Response = vbYes Then ' User chose Yes
FormatAns = "Yes"
Else ' User chose No.
FormatAns = "Yes"
End If
<End Code>

Regardless of the button clicked, "FormatAns" is "Yes" and the drive is likely to
be
reformatted.

I consider this a "software error". Do you concur?

Only if the user doesn't wish to format the hard drive.

Do you consider the example provided above a "software error"? A narrative answer is
not required. A simple "Yes" or "No" will suffice.> <snip "Deer Hunter" reference>

So nice try; but again no cigar

Pardon? The question posed was: "can you give an example of what you yourself would
consider a 'software error'"

Are you saying that you do not consider the example provided demonstrates a software
error?

There is no way of knowing.

The same would therefore be true of your example.

But that's not what you said in

quote:

Simon Parker" <simonparkerulm@gmail.com> wrote in message news:l2urqjF4d1vU12@mid.individual.net...

I accept that you have provided an example of a software error"

:unquote

Is it ?

A statement which did still appear in the material which has been snipped

While I never claimed that your example definitely *was* a software error, in fact you
we keen to press me on the matter, you had no hesitation at all in claiming that
mine was !

Also please note I have actually quoted the relevant text. Rather than simply leave the message ID and expect the reader to ....

<Ctrl> + <Shift> + F
Enter / Paste the "Message-ID" into the search box
Click the "Search" button
Double-click the message

Please also note (in answer to a query in another post) that by appending
a 5 at the end of this *subthread* I was immediately able to identify the
post containing the above statement

Because while you may have commented the actual code what is
conspicuously lacking is any explanation of that piece of code
is actually intended to achieve

Which in properly documented code would normally expected
at the start

The same would therefore be true of your example, which contained no comments whatsoever.

But that's not what you said before is it ? Then there was no mention
of documentation there was there? Just

Simon Parker" <simonparkerulm@gmail.com> wrote in message news:l2urqjF4d1vU12@mid.individual.net...

I accept that you have provided an example of a software error"

>

As I've explained to you more than once now, a software "fault" arises
when program or piece of code doesn't achieve the result which was
intended.

Which in repose to point made earlier or maybe quoted from somewhere else, won't always be evident no matter how closely the code is examined. And regardless of how well documented it is.,


< remainder snipped >

bb

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)