Bakul Shah wrote:
On Mon, 12 Feb 2018 10:33:51 -0800 Paul Vixie wrote:
if we wanted the effort of an actual rewrite, we would need to justify
the time expenditure with a potentially larger user population, which
means reconsideration of features that younger people actually
David Levine wrote:
Ralph wrote:
The aim would be for the existing users to
have a code base that allowed more rapid, stable development of new
features, deprecating old warts, and improving consistency.
+1
I'd rather see more of all the above, even if it means giving up some
current
On Mon, 12 Feb 2018 10:33:51 -0800 Paul Vixie wrote:
>
> if we wanted the effort of an actual rewrite, we would need to justify
> the time expenditure with a potentially larger user population, which
> means reconsideration of features that younger people actually depend
>
On Mon, 12 Feb 2018 15:26:18 -0800 Paul Vixie wrote:
>
> Ken Hornstein wrote:
> ...
> > you said:
> >
> >> And the programs I tried worked fine. Running best scan time
> >> for 200K messages, scan+gc takes 13.5 seconds while the
> >> regular scan 7.4 seconds.
> >
> > To me a
Ralph wrote:
> The aim would be for the existing users to
> have a code base that allowed more rapid, stable development of new
> features, deprecating old warts, and improving consistency.
+1
I'd rather see more of all the above, even if it means giving up some
current capabilities. I don't
Paul V wrote:
> note: because valgrind finds hundreds of thousands of runtime anomalies
> in even a trivial libcurl application, and because the suppression file
> syntax for valgrind doesn't permit me to say "if it comes from libcurl
> just ignore it",
Doesn't something like this?
{
if
Ken Hornstein wrote:
Some smart-ass on this list recently gave me a flippant response when
I made a similar lament regarding valgrind on MacOS X. Who was that
again? :-)
i normally hate people like that, but did he say, here kid, here's a
nickel, get yourself a better C library for
>> Looks like that was introduced in ff5eb06992. It looks like ... that
>> gets called if it is parsing a component with multiple addresses and
>> the first one is NOT one of your local mailboxes, but later ones are?
>> Maybe. Ralph, does that match the description of your message?
>
>It's in
>note: because valgrind finds hundreds of thousands of runtime anomalies
>in even a trivial libcurl application, and because the suppression file
>syntax for valgrind doesn't permit me to say "if it comes from libcurl
>just ignore it", i'm currently at wit's end in verifying my heap memory
Ken Hornstein wrote:
...
you said:
And the programs I tried worked fine. Running best scan time
for 200K messages, scan+gc takes 13.5 seconds while the
regular scan 7.4 seconds.
To me a performance penalty of 50% is not worth it, but I'd be willing
to hear from others.
the various design
>There was a fair bit of variability but it was no worse than
>twice as slow and often close to par.
Um ... are we looking at the same results? Because I would classify
the results as "on average, more than twice as worse", and I could NOT
in any universe say "often close to par" (I am going by
On Mon, 12 Feb 2018 09:27:04 + Ralph Corderoy wrote:
Ralph Corderoy writes:
> Hi Paul,
>
> > i just don't know whether MH can attract new users through a rewrite.
>
> That wouldn't be the aim. The aim would be for the existing users to
> have a code base that allowed
On Mon, 12 Feb 2018 17:35:13 -0500 Ken Hornstein wrote:
Ken Hornstein writes:
> >As I showed, the perf loss via
> >using GC with nmh is tolerable and this is without doing any
> >cleanup or code improvement based on profiling.
>
> Errr ... were there some other messages where
>As I showed, the perf loss via
>using GC with nmh is tolerable and this is without doing any
>cleanup or code improvement based on profiling.
Errr ... were there some other messages where this assertion was made?
Because my takeway was that with garbage collection it was MUCH MUCH
worse. Like,
On Mon, 12 Feb 2018 13:15:08 -0800 Paul Vixie wrote:
>
> Ralph Corderoy wrote:
> >
> >> he wanted new(), and methods, and garbage collection.
> >
> > GC as in https://en.wikipedia.org/wiki/Smart_pointer#Features ?
> > So analyse and switch from C pointers to the various C++
Ralph Corderoy wrote:
Hi Paul,
that's a knee-jerk reaction.
Very true. A regurgitation of a long-held view.
bert hubert at powerdns found a subset he can live with, and ways to
enforce it. basically there are no operators overloaded and no
subclassing.
I've struggled to find something
Hi Paul,
> that's a knee-jerk reaction.
Very true. A regurgitation of a long-held view.
> bert hubert at powerdns found a subset he can live with, and ways to
> enforce it. basically there are no operators overloaded and no
> subclassing.
I've struggled to find something on this, e.g. a guide
Hi Paul,
> if we wanted a better code base for the same graying user population,
> wouldn't we do a gradual rewrite in some well-disciplined subset of
> C++ instead?
No, everyone has a difference subset so we won't agree. There's nothing
to enforce it automatically. No subset of C++ is nice.
Ken Hornstein wrote:
...
But ... one nasty problem raises it's head. That is the lack of _time_.
We have plenty of great ideas, but those of us who want to implement
them all suffer from a lack of time to work on them. Rewriting nmh in
Go seems like it would take a long time. Slowly
>For example, whilst I like the Unix idiom of one command to do one thing
>well, I do find myself doing a series of picks, marks, and scans to
>whittle down emails whereas having a consistent, planned, notation that
>can be used wherever a message number can be given would lessen the
>iterations a
>I ideally ask because of an off-list comment received of being tempted
>to re-write nmh in Go. That would be my first choice in starting today
>too. I've been programming C on Unix since the 80s, and it's seen off
>inferior allcomers like Java and C++, but Go is the one to replace it
>for many
Hi Paul,
> i just don't know whether MH can attract new users through a rewrite.
That wouldn't be the aim. The aim would be for the existing users to
have a code base that allowed more rapid, stable development of new
features, deprecating old warts, and improving consistency.
For example,
i do all new work in Go.
i just don't know whether MH can attract new users through a rewrite.
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Hi,
Do you run nmh on an OS and architecture that isn't in this list?
If so, what version of MH/nmh, OS, and architecture?
androidarm
darwin 386 amd64 arm arm64
dragonfly amd64
freebsd386 amd64 arm
linux 386 amd64 arm arm64
24 matches
Mail list logo