[arachne] Re: arachne Digest V2 #292

Arachne at FreeLists---The Arachne Fan Club!

> From: "Greg Mayman" <gmone@xxxxxxxxxx>

Hi Greg,

>>  Whether if ever ends up as
>> standard equipment is questionable, but Michal and I are seriously
>> considering the idea that there should be a special DEBUG version of
>> the core that folks could use in place of the standard version for
>> industrial strenth diagnostic purposes; it would have less free memory
>> but other than that it would work exactly the same (apart from the
>> diagnostics that it would perform of course).

> Again we come up with the same problem: you'd have to make a
> DEBUG version of every new core.

That's no problem, since the code in question would be conditional
('#define DEBUG' and the code is active), so building cores with and without
that code in effect would be simple for any forthcoming version.

>> Anyway, I've already found it invaluable since it makes it childs play
>> to diagnose anything that's gone wrong with configuration.

> Yes, I agree 110% with that!
> I'd like to see it in every version.

>> The output from this current session looks like this:

> That is very clear!

Yes, it is easy to see what's happening and I continue to find new
ways to play with it, for example, in case of trouble with arachne.cfg,
one can rename config.bat >> arachne.cfg and Arachne is quite happy to
use the former in place of the latter.

> I have been using QEDIT in a two-window setup to compare a
> problem config with a known good one. With the windows set to
> scroll in sync, it is easy enough to visually check them, until
> something gets out of step.

> At one stage in desparation I wrote a QBASIC program to read the
> new config file line by line, and open the old one and search
> through it for the line starting with the same word. If the lines
> were not the same, it would print both the old and new version.
> Then using the printout I could go in and alter the new config
> file as needed.

Yup, I'm sure most of us have done this sort of thing.  With
CONFIG.LOG the process is much simpler since all extranious material is
gone, and the options are always listed in the same order, so there are
no differences between two copies of the log which aren't 
significant.

Shall I send you a copy for your evaluation?

Ray Andrews

-- Arachne V1.75++/B~5


Arachne at FreeLists
-- Arachne, The Web Browser/Suite for DOS and Linux --

Other related posts: