[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mhbuild and long header fields
From: |
Philipp |
Subject: |
Re: mhbuild and long header fields |
Date: |
Mon, 28 Aug 2023 11:53:24 +0200 |
[2023-08-27 22:00] David Levine <levinedl@acm.org>
> Philipp wrote:
>
> > [2023-08-27 09:29] David Levine <levinedl@acm.org>
> > >
> > > My only comment on the code itself is that I prefer functions that
> > > just do one thing. So I would implement a fold function that just
> > > modifies a string, and leave the fprintf/fwrite to output_headers().
> >
> > I have thought about this, but this would require fold() to allocate memory.
> > Because the plan was to use fold() in output_headers() I though this could
> > be avoided.
>
> I don't think that allocating memory is a drawback.
I first wrote a long text about the missing string abstraction, then
I found charstring_t. I'll adjust this a few days.
One question about charstring_t: Why does charstring_push_back_chars()
not use memcpy?
Philipp
- Re: mhbuild and long header fields, (continued)
- Re: mhbuild and long header fields, Steffen Nurpmeso, 2023/08/25
- Re: mhbuild and long header fields, Philipp, 2023/08/25
- Re: mhbuild and long header fields, David Levine, 2023/08/26
- Re: mhbuild and long header fields, Philipp, 2023/08/27
- Re: mhbuild and long header fields, David Levine, 2023/08/27
- Re: mhbuild and long header fields, David Levine, 2023/08/27
- Re: mhbuild and long header fields, Philipp, 2023/08/27
- Re: mhbuild and long header fields, David Levine, 2023/08/27
- Re: mhbuild and long header fields, Philipp, 2023/08/28
- Re: mhbuild and long header fields, David Levine, 2023/08/28
- Re: mhbuild and long header fields,
Philipp <=
- Re: mhbuild and long header fields, David Levine, 2023/08/28
- Re: mhbuild and long header fields, Philipp, 2023/08/31
- Re: mhbuild and long header fields, David Levine, 2023/08/31
- Re: mhbuild and long header fields, David Levine, 2023/08/20