9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Arne Meyer <meyer.arne83@netcologne.de>
To: 9front@9front.org
Subject: Re: [9front] [patch] skelfs: remove useless code
Date: Fri, 11 Nov 2022 18:52:14 +0100 (CET)	[thread overview]
Message-ID: <1453278421.4596864.1668189134709@comcenter.netcologne.de> (raw)
In-Reply-To: <6c58605e-7b25-1adc-3681-41df77e4ae91@posixcafe.org>

After that patch I grepped through /sys/src/cmd/* and found a more hits. Is there any difference between handrolled emalloc implementations and emalloc9p? If not, I can go spelunking to replace emalloc where emalloc9p is available.

> Jacob Moody <moody@mail.posixcafe.org> hat am 11.11.2022 17:37 GMT geschrieben:
> On 11/11/22 10:17, Arne Meyer wrote:
> > Hello,
> >   
> > if I read the code correctly emalloc9p already checks for failed allocations and zeroes the memory, so the following code is redundant.
> > 
> > Greetings,
> > Arne
> You are correct, muscle memory did not work in my favor this time.
> Thanks!
> moody

  reply	other threads:[~2022-11-11 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 17:17 Arne Meyer
2022-11-11 17:37 ` Jacob Moody
2022-11-11 17:52   ` Arne Meyer [this message]
2022-11-11 19:20     ` Jacob Moody
2022-11-12 10:20       ` Arne Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1453278421.4596864.1668189134709@comcenter.netcologne.de \
    --to=meyer.arne83@netcologne.de \
    --cc=9front@9front.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).