From: Rusty Russell <rusty@rustcorp.com.au>
To: ccan <ccan@lists.ozlabs.org>
Subject: CCAN update for 2015-11
Date: Thu, 03 Dec 2015 14:27:23 +1030 [thread overview]
Message-ID: <8737vk6v6k.fsf@rustcorp.com.au> (raw)
Hi!
A quiet month, but I found myself needing an fd-returning fopen
call, so wrote pipecmd. Much more activity over graph traversal from
David Gibson.
Module of the Month: cast (LGPL2.1+)
====================================
This is a simple module which provides macros to make casting safer and
more explicit. In particular, "cast_const(char *, foo)" gives a warning
if foo isn't a "const char *". Similarly, cast_signed() will only change
signedness, and cast_static() will only do casts which would have been
implicit in C.
New modules:
============
pipecmd: fork a command with explicit fds attached.
Updates & bugfixes:
========================
aga: many minor fixes, documentation updates (David Gibson)
aga, agar: Dijkstra's algorithm (David Gibson)
net: use close_noerr()
noerr: add free_noerr()
strgrp: add cosine similarity filter (Andrew Jeffery)
Cheers,
Rusty.
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
reply other threads:[~2015-12-03 3:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8737vk6v6k.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ccan@lists.ozlabs.org \
/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