comp-hist-devel

[Comp-hist-devel] Parsech plans

[Scott F. <sj...@ra...>]

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

-- 
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM
XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI
iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX
n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW
10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS
jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv
Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT
t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL
K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu
dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID
FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX
OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U
tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx
M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M
SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA
UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz
uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+
iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV
5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1
=tjOP
-----END PGP PUBLIC KEY BLOCK-----

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

Re: [Comp-hist-devel] Parsech plans

[Scott F. <sj...@ra...>]

On Wed, Nov 29, 2000 at 08:52:37PM -0500, the keyboard of Kurt Raschke was alleged to have written:
> 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?

That could work. I'll look into it after the big split.

> 
> 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.
> 

That's a little hard to engineer. What the parser thinks as it 
looks through the file is something like this: "gee does this
field match this regexp?" It would be kinda hard to set it to
flag an error when it sees one.

> -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
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...  
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel

-- 
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM
XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI
iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX
n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW
10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS
jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv
Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT
t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL
K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu
dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID
FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX
OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U
tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx
M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M
SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA
UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz
uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+
iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV
5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1
=tjOP
-----END PGP PUBLIC KEY BLOCK-----