mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ivan Kanakarakis <ivan.kanak@gmail.com>
To: musl@lists.openwall.com
Subject: Re: New articles on ewontfix
Date: Fri, 5 Jul 2013 18:45:27 +0300	[thread overview]
Message-ID: <CAJnvVWW1K9sdAPrZB61e12G05bftmZ=Y+DHFbnwk0R44qLc93w@mail.gmail.com> (raw)
In-Reply-To: <B1AAE143-9BC4-41C6-9431-E214FEBBD344@lightcubesolutions.com>

[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]

I am waiting for the "library-safe" article ;)




On 5 July 2013 18:31, Jeremy Huntwork <jhuntwork@lightcubesolutions.com>wrote:

> On Jul 4, 2013, at 1:58 PM, Rich Felker <dalias@aerifal.cx> wrote:
>
> >> I really enjoyed these, thanks!
> >
> > Thanks for the feedback. BTW, I think it's really nice how the
> > widespread adoption of version control systems and web interfaces for
> > them has made it possible to cite source so easily, in such a way that
> > readers can go directly to the code I'm talking about and see for
> > themselves what it's doing.
>
> Yep, it's at the point now where you can pretty much take it for granted.
> Only after you commented did I recall what it was like a few years back
> when typically the best you had was grabbing a cvs snapshot for yourself
> and examining the code locally.
>
> Rich, you have the rare ability of being able communicate technical
> details in a way that is easy to understand and not horribly dry to read.
> If you ever have time and motivation, I would love to read an article from
> you about what makes good software.  For example, pitfalls to avoid in C
> (esp. ones that even experienced devs fall into). Or good design decisions
> on the Unix/Linux platform vs poor design decisions - writing good code
> that is both efficient and scalable.
>
> I know you're busy and many of these things one can find piecemeal on the
> internets. (E.g., Rob Landley has some good thoughts on his toybox list
> about cleaning up code contributions to toybox.) Still, having one good
> article that is a joy to read makes a huge difference.
>
> JH




-- 
*Ivan c00kiemon5ter Kanakarakis*  >:3

[-- Attachment #2: Type: text/html, Size: 2521 bytes --]

  reply	other threads:[~2013-07-05 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 16:48 Rich Felker
2013-07-04 17:50 ` Jeremy Huntwork
2013-07-04 17:58   ` Rich Felker
2013-07-05 15:31     ` Jeremy Huntwork
2013-07-05 15:45       ` Ivan Kanakarakis [this message]
2013-07-05 15:54         ` Rich Felker
2013-07-07 12:20           ` Szabolcs Nagy
2013-07-07 15:27             ` Rich Felker
2013-07-07 15:52               ` Daniel Cegiełka
2013-07-07 17:12               ` Szabolcs Nagy
2013-07-07 17:53                 ` Rich Felker
2013-07-08 11:39 ` LM

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='CAJnvVWW1K9sdAPrZB61e12G05bftmZ=Y+DHFbnwk0R44qLc93w@mail.gmail.com' \
    --to=ivan.kanak@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).