From 59fa35679d83dd2e4d0cf13c2a1d2cf8fbb9de76 Mon Sep 17 00:00:00 2001 From: markus schnalke Date: Sat, 24 Mar 2012 18:59:41 +0100 Subject: [PATCH] Removed the now irrelevant parts of the ``history section'' in m_getfld.c. --- sbr/m_getfld.c | 54 ++++++++++-------------------------------------------- 1 file changed, 10 insertions(+), 44 deletions(-) diff --git a/sbr/m_getfld.c b/sbr/m_getfld.c index df48026..85a323b 100644 --- a/sbr/m_getfld.c +++ b/sbr/m_getfld.c @@ -10,51 +10,18 @@ #include /* -** This module has a long and checkered history. First, it didn't burst -** maildrops correctly because it considered two CTRL-A:s in a row to be -** an inter-message delimiter. It really is four CTRL-A:s followed by a -** newline. Unfortunately, MMDF will convert this delimiter *inside* a -** message to a CTRL-B followed by three CTRL-A:s and a newline. This -** caused the old version of m_getfld() to declare eom prematurely. The -** fix was a lot slower than +** This module has a long and checkered history. ** -** c == '\001' && peekc (iob) == '\001' +** [ Here had been some history of delimiter problems in MMDF maildrops ... ] ** -** but it worked, and to increase generality, MBOX style maildrops could -** be parsed as well. Unfortunately the speed issue finally caught up with -** us since this routine is at the very heart of MH. +** Unfortunately the speed issue finally caught up with us since this +** routine is at the very heart of MH. To speed things up considerably, the +** routine Eom() was made an auxilary function called by the macro eom(). +** Unless we are bursting a maildrop, the eom() macro returns FALSE saying +** we aren't at the end of the message. ** -** To speed things up considerably, the routine Eom() was made an auxilary -** function called by the macro eom(). Unless we are bursting a maildrop, -** the eom() macro returns FALSE saying we aren't at the end of the -** message. +** [ ... and here had been some more of it. ] ** -** After mhl was made a built-in in msh, m_getfld() worked just fine -** (using m_unknown() at startup). Until one day: a message which was -** the result of a bursting was shown. Then, since the burst boundaries -** aren't CTRL-A:s, m_getfld() would blinding plunge on past the boundary. -** Very sad. The solution: introduce m_eomsbr(). This hook gets called -** after the end of each line (since testing for eom involves an fseek()). -** This worked fine, until one day: a message with no body portion arrived. -** Then the -** -** while (eom(c = getc(iob), iob)) -** continue; -** -** loop caused m_getfld() to return FMTERR. So, that logic was changed to -** check for (*eom_action) and act accordingly. -** -** [ Note by meillo 2011-10: -** as msh was removed from mmh, m_eomsbr() became irrelevant. ] -** -** This worked fine, until one day: someone didn't use four CTRL:A's as -** their delimiters. So, the bullet got bit and we read mts.h and -** continue to struggle on. It's not that bad though, since the only time -** the code gets executed is when inc (or msh) calls it, and both of these -** have already called mts_init(). -** -** [ Note by meillo 2012-02: -** MMDF-style maildrops (4x ^A) and mts_init() were removed. ] ** ** ------------------------ ** (Written by Van Jacobson for the mh6 m_getfld, January, 1986): @@ -76,9 +43,8 @@ ** If you hack on this and slow it down, I, my children and my ** children's children will curse you. ** -** This routine gets used on three different types of files: normal, -** single msg files, "packed" unix or mmdf mailboxs (when used by inc) -** and packed, directoried bulletin board files (when used by msh). +** This routine gets used on two different types of files: normal, +** single msg files and "packed" unix mailboxs (when used by inc). ** The biggest impact of different file types is in "eom" testing. The ** code has been carefully organized to test for eom at appropriate ** times and at no other times (since the check is quite expensive). -- 1.7.10.4