[prev in list] [next in list] [prev in thread] [next in thread] 

List:       imp
Subject:    Re: [imp] address parsing
From:       Chuck Hagenbuch <chuck () horde ! org>
Date:       1999-03-15 20:33:38
[Download RAW message or body]

Quoting Ivan E. Moore II <rkrusty@tdyc.com>:

> well it does and it doesn't...I'm doing more that what this function can
> do (or is designed to do)...and therefore this isn't a complete solution
> whereas the regex does...

Why doesn't this do everything you need? Sure, you need to add a few ifs to
fill in bits that might come back empty, but it *doesn't* use a regex, it's
built in and therefore maintained and fast...

> get address being passed from the message.php3 session...so far no matter
> what it comes in a    Blah <blah@blah.com>   format.  

This is a *bad* assumption to make. It'd be nice if changing, say, how we
displayed the message headers didn't break inserting addresses into the
addressbook.

> I personally think the code I'm using works just as easily with just as much
> (maybe a bit more) code as the above function.  Plus I get more functionality.

I still don't see what additional functionality you get. Then again, *I* may
be wrong too. :) At any rate, I'll rewrite it if you want, instead of just
spouting off - let me know.

-chuck

--
Charles Hagenbuch     | "The streets are bare and everywhere the trees
chuck@horde.org       |  are full of strangers..." - apologies to Les Mis

--
IMP mailing list: http://web.horde.org/
To unsubscribe, e-mail: imp-unsubscribe@horde.org
For additional commands, e-mail: imp-help@horde.org

[prev in list] [next in list] [prev in thread] [next in thread]