Re: [Comp-hist-devel] Parsech plans

[Kurt R. <ku...@ra...>]

I have two ideas:
1.  Why not create some sort of text-based spreadsheet-like output format for getting a quick visual overivew of a node's stats?

2.  It might be nice if there was a option to parsech that would flag and print a note about errors found in the input, instead of silently ignoring them.

-Kurt
On Wed, Nov 29, 2000 at 08:27:59PM -0500, Scott Fenton wrote:
> OK, if any of you have been paying attention to CVS lately,
> you'll notice that I've been making quite a few changes to
> parsech. I'm writing this to explain these changes, and 
> why I'm doing them.
> 
> First, the what. I'm working to make each subroutine less
> dependent on others. Ulimatly, there will only be the %Opts
> hash as a universal variable. Even though I haven't checked
> it into CVS yet (there are a few kinks in the system), I've 
> begun the final stage of all of this on one of the subs.
> 
> Now, the why. Quite simply, I'm working to break up parsech.
> I believe it has become an ugly hairball that will be
> impossible to maintain eventually. I'm going to give ParseCH.pm
> another try, see if I can get it this time.
> 
> Thoughts? Suggestions? Jelly doughnuts? Reply with them.
> 
> -Scott
> 
> -- 
> pub  1024D/B5A525FA 2000-08-26 Scott Fenton <sj...@ra...>
> sub  1024g/A41E2502 2000-08-26 
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...  
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel