From: Rusty Russell <rusty@rustcorp.com.au>
To: ccan <ccan@lists.ozlabs.org>
Cc: Cody P Schafer <dev@codyps.com>, Lana Brindley <mail@lanabrindley.com>
Subject: CCAN update for 2015-09
Date: Thu, 01 Oct 2015 14:38:47 +0930 [thread overview]
Message-ID: <87twqbnpk0.fsf@rustcorp.com.au> (raw)
Hi fellow CCANnibals!
Some tools work this month; makes me wonder how many people have
ever read the ccanlint man page? I think it was Lana Brindley who
promised me that writing bad documentation was a great way to get others
to fix it. "man -l doc/ccanlint.1" in the ccan repo, or read the source:
https://github.com/rustyrussell/ccan/blob/master/doc/ccanlint.1.txt
Module of the Month: mem (CC0)
==============================
All kinds of routines which didn't make stdlib, such as simple clarity
increasers like memeq(a,alen,b,blen), memeqstr(a,alen,str) and
memoverlaps(a,alen,b,blen). There's also memswap(a,b,len) and
mempbrkm(a,alen,b,blen) which looks for any of "b" chars in "a".
There's also the pass-through memcheck(a,alen) which checks the memory
is defined if running under valgrind.
New modules:
============
strgrp - group/cluster similar strings. (thanks Andrew Jeffery)
permutation - Generate permutations of arrays (thanks David Gibson)
Minor updates & bugfixes:
========================
mem: many new routines (thanks Cody Schafer, David Gibson)
Tools updates:
=============
configurator: enhancements to detect OpenMP (thanks Andrew Jeffery)
_info: can now specify additional cflags (thanks Andrew Jeffery)
ccanlint: better handling of "// given" example tests.
Cheers,
Rusty.
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
reply other threads:[~2015-10-01 5:45 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=87twqbnpk0.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ccan@lists.ozlabs.org \
--cc=dev@codyps.com \
--cc=mail@lanabrindley.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox