briarpig: code

BSD

All cy code has a BSD license with one restriction: avoid lowercase y as a first letter in global symbol names (for example, class names).

copyright

All the cy code has this copyright:

The purpose of BSD-licensed cy code is to provide an open source version of my y thorn library which you can use as you wish under a liberal license. The c prefix is a pun, meaning both see and the C programming language. Some of the uglier cy kludges are pragmatic bridges to C only environments.

license

Here's a license and copyright notice you must maintain with copies. Note this license applies exclusively to code appearing at a URL containing /cy/ in the path on this site. C++ symbols appear in namespace cy, or else begin with a cy_ prefix.

Copyright (c) 1993-2009 David McCusker All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

menu

Here's a menu of pages on cy code.

vector - std::vector clone
bheap - binary min heap
label - async descriptors
misc - bunch of basic utils
pool - C-based vats and pools
deck - scatter/gather suite
sink - C-based out stream api
row - a new deck rewrite

spoon

(I don't care whether there is or isn't a spoon. The matrix image at right is just a fun nod. I have no deep message to convey; a spoon joke merely highlights this.)

first name

I go by Rhys, but I usually omit the h. (The shorter version is Czech for Bobcat, but that's not what I had in mind.) I ascribe a Welsh neologism to the short version. It matches my use of such first names in fiction.

I like a low profile online. So I thank you to avoid pointing to me by name.

bugs

I expect you'll find bugs in the cy code, especially since my standard of care is lower here, when my goal is just to show how to do something so you can adapt code as you like. You must not demand bug fixes.

If you send email to david at briarpig (of couse, with dot com appended) I might fix bugs you find. I might even reply; but a reply seems unlikely unless I fix code.

kludges

A few cy conventions may look strange. Most of these are motivated by use of cy inside C-only systems with anti-C++ restrictions, such as not linking any standard C++ library.

For example, putting all memory management in the hands of C code is especially awkward. But you can still do it ... if you don't mind how ugly it looks, and I don't.