Hej Anders,

If you re-read my mail you will see that my comments referred specifically
to the High CPU Load problem that Kenny experienced and referred to in this
thread and to which Noel replied. My comments were appended to those. Maybe
I could have cut this across to the original "High CPU Load" thread, but
both Kenny's and Noel's comments and my intent seemed clear (to me).

I leave the debate as to the usefulness of James error messages to others.

-- Steve



> -----Original Message-----
> From: boxed [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2003 18:28
> To: James Users List
> Subject: Re: Useful error messages
>
>
> Steve Brewin wrote:
>
> >Where in the commercial world would a new and relatively
> obscure bug such as
> >this be diagnosed and fixed in this time-frame? I would
> rather view this in
> >a positive light, as a demonstration of how effective OSS can be.
> >
> >
> >
> New and obscure? If the user makes any mistake in the config file
> they'll get this type of errors. Editing the config file is
> pretty much
> the first thing you do when setting up a program, so I can't see how
> it's new or obscure. As for "fixed"? Stephens email strongly suggests
> this is a design flaw that is repeated over and over in the
> code. Fixing
> it in one place doesn't change anything. Furthermore, what
> about syntax
> errors in the xml file? Will I get a line number if I get the new
> version from CVS?
>
> >Noel, with the benefit of hindsight you are seeing how the
> bug might have
> >been removed earlier, but that doesn't imply a lack of
> foresight. And let's
> >remember, we're talking about an alpha release of James here.
> >
> >
> >
> Someone actually wrote _more code than needed_ to produce
> this problem.
> That's not a matter of "removed earlier".
>
> Anders Hovmöller
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to