[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IMAP4 parsing
From: |
Alain Magloire |
Subject: |
Re: IMAP4 parsing |
Date: |
Mon, 15 Jan 2001 21:47:54 -0500 (EST) |
>
> On Mon, Jan 15, 2001 at 10:53:55AM -0500, Alain Magloire wrote:
> >
> > Somebody have a good approach on dealing that "lips"y parsing of the
> > IMAP4d server. Sorry for emacs/scheme/lips/guile etc but every time I look
> > at this I have to take a few step back.
>
> What are you trying to do, Alain I'm not very good at Scheme, but I've
> done a few things in it.
That's ok, I think it was from frustration, parsing stuff like below
to only know how many parts in a message is annoying at best:
* 1 FETCH (BODY ((("TEXT" "PLAIN" ("CHARSET" "US-ASCII") "<address@hidden>" N
IL "8BIT" 13 1)("TEXT" "PLAIN" ("CHARSET" "US-ASCII") "<address@hidden>" NIL
"8BIT" 13 1) "MIXED")("TEXT" "PLAIN" ("CHARSET" "US-ASCII") "<address@hidden>
" NIL "8BIT" 12 1)("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 0 0) "MI
XED"))
and frankly @*&$&(#^ when some quote strings ("") can be broke to be a
literals,... grr. I did the parsing for the client side (mailbox library),
not totally satisfy with the end result.
Looking at imap4d/*, I was less then "enthousiastic"(sp?) to do the exercise.
It will probably be less painfull but this time I would prefer a cleaner way.
I do not know if Jakob had something in mind, when he wrote the first
framework for imap4d/*.[ch]
--
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!