From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] test(1) -older bug?
Date: Mon, 3 Jun 2013 09:02:24 -0400 [thread overview]
Message-ID: <4b62d76ce093e2671c186984dca965a3@brasstown.quanstro.net> (raw)
In-Reply-To: <201306031100.r53B0eCt025839@freefriends.org>
On Mon Jun 3 08:00:20 EDT 2013, arnold@skeeve.com wrote:
> Richard Miller <9fans@hamnavoe.com> wrote:
>
> > And the consequences of not freeing a few bytes of memory, in a command
> > which will exit a few microseconds later, would be ... ?
>
> The Code Correctness Police come and collect you and force you to
> program on Windows... <ducks>
excellent points. there is no consequence. but conversely, there is
no penalty for free'ing the memory either. given that, i prefer free'ing
the memory to be consistent with the rest of the source, and accept
cinap's bug as a bug.
of course you can say needless consistency is the hobgoblin of little
minds...
:-)
- erik
next prev parent reply other threads:[~2013-06-03 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 21:15 arisawa
2013-06-01 21:59 ` erik quanstrom
2013-06-02 21:29 ` cinap_lenrek
2013-06-03 3:44 ` erik quanstrom
2013-06-03 10:47 ` Richard Miller
2013-06-03 11:00 ` arnold
2013-06-03 13:02 ` erik quanstrom [this message]
2013-06-03 11:08 ` Jacob Todd
2013-06-03 11:12 ` Richard Miller
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b62d76ce093e2671c186984dca965a3@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).