Re: Log_Parser - New maintainer? Delete?
| From: | anatoly techtonik | Date: | Fri, 14 Jan 2005 14:49:15 +0000 |
| Subject: | Re: Log_Parser - New maintainer? Delete? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35491@lists.php.net to get a copy of this message | ||
Hello Tobias,
TS> As the lead maintainer of Log_Parser, I'm searching for someone new to
TS> maintain (or better, first: implement) this package.
TS> The idea for Log_Parser was born in my last company for a specific
TS> project, which then was cancled in a very early stadium. A few month
TS> after that, Peter P. stated interesst in implementing the class for a
TS> project in his company, which seems also obsolete by now. Because of
TS> this Log_Parser has never really seen the light of the world.
TS> Is there anyone interessted in stepping into this project? I would
TS> definitly like to assist there, but have neither time for it, nor any
TS> project where I could use it, by now.
TS> If nobody volunteers to come on board with this, I'd like to simply
TS> delete the package. This should not make any problems, because it's
TS> never seen a release by now.
I already have many solutions for parsing logs, email letters, news,
web-sites, php sources, but I don't have any solid universal solution
to separate it in another package. Most of the time it is
preg_match_all operation and some more heavy logic, appropriate for
specific situation. IMHO unified solution would be only complex syntax
checking engine with some finite state machine analyzer. It surely
complex, requires some serious planning and I can't see how this
could be implemented. I don't think preg_match_all deserves to be
encapsulated in a class because it is simplier, faster, smaller and
hence better to use it without objects.
The only purpose of this can be to teach developers how to use regex
from PEAR docs also, but this is definitely not a thing among few of
those where I'm good.
Once more from my POV log parser is not any simplier than XML parser.
Even more complex, because you need to define well-formedness criteria
by yourself. It is the situation, where tools worth more, than end
products, so to grant success to this package (make it useful), it
should implement some editing/testing/debugging/composition framework
for log rules first.
t
--