[Chicken-users] LevelDB bindings

Hi all, I'm new to the list (and CHICKEN) *waves* I thought I'd have a go at writing an egg and put together some bindings to Google's LevelDB embedded key/value store. I've published it at https://github.com/caolan/chicken-leveldb Can someone please help me with getting it onto the egg index?

Re: [Chicken-users] LevelDB bindings

Thanks Evan, I've renamed the directory to 'tests'. Salmonella still complains about missing docs, not sure how to fix that. Caolan On 20 April 2014 14:23, Evan Hanson ev...@foldling.org wrote: Hi Caolan, and welcome :) Thanks for making this egg -- based on the README it looks very nice to

Re: [Chicken-users] LevelDB bindings

Thanks, I've updated the wiki. Alex: the output from the conversion seemed a little broken so I ended up converting by hand. Perhaps try running it on the README.md file yourself to see what went wrong? On 20 April 2014 15:25, Alex Charlton alex.n.charl...@gmail.com wrote:

Re: [Chicken-users] Chicken Spring Gathering in Norway

I'd gladly host you in Sheffield, UK if that interests any of you ;) On 11 May 2014 19:48, Moritz Heidkamp mor...@twoticketsplease.de wrote: Hey Kristian and Peder, Kristian Lein-Mathisen krist...@adellica.com writes: I would just like to thank everybody who attended the Viking CHICKEN

[Chicken-users] fnmatch egg

I've just written some bindings to fnmatch(3), which provides shell-style wildcard pattern matching for filenames. Much like `glob` from the posix module, only it matches two strings, returning a boolean rather than descending directories and returning a list of matching filenames.

[Chicken-users] New leveldb eggs

I published leveldb bindings a while ago. It turns out the implementation had some issues with mangled keys in some circumstances. I've now fixed these issues and created some additional eggs to compliment leveldb. The new eggs are as follows: level - provides the leveldb interface (put/get etc)

Re: [Chicken-users] New leveldb eggs

I'm hoping to write (or encourage someone else to write) a memory-only implementation of the 'level' API, which would be useful for testing or other circumstances where you want to use a module written to the 'level' interface without persisting data. Sounds useful. And perhaps some

[Chicken-users] TOML parser egg

Hi all, I've been writing a TOML parser, mostly as an excuse to play with comparse (with is very nice btw). TOML is a reasonable looking config file format that's not crazy like YAML ;) The egg is available at http://github.com/caolan/chicken-toml More info on TOML:

Re: [Chicken-users] Statically Linking Eggs

I'm also interested in the tooling around statically linked eggs, or at least finding ways to better document the process. I've had mixed results, sometimes it's easy, others it's incredibly painful. If anyone has ideas on how to improve this I'd be willing to help out. On 19 May 2015 at 06:18,

[Chicken-users] CommonMark parser (please add to egg index)

I've written some simple bindings to the cmark C library for parsing CommonMark (a more highly specified MarkDown): https://github.com/caolan/chicken-cmark Please add this to the egg-locations file in SVN, as I don't have the appropriate permissions :) (cmark

[Chicken-users] Bencode egg

Hi all, I've just written a quick egg to do Bencode parsing / serialization. Bencode is the encoding used by BitTorrent, and is similar to tagged-netstrings. Bencode supports four data types: * Strings * Integers * Lists * Dictionaries Bencode uses ASCII characters as delimiters and digits,

[Chicken-users] ldap-bind egg

Please add this to the egg index: https://github.com/caolan/chicken-ldap-bind It provides basic bind functionality for authenticating a user with an LDAP server - it's not a full OpenLDAP binding, but hopefully it's still useful. Thanks to Moritz Heidkamp for doing most of the hard work. I was

Re: [Chicken-users] another egg

to you (and may > go the coop): > > http://askemos.org/chicken-eggs/raspberry-pi-gpio-small.release-info > > This is a (supposed to be) API compatible version of the > raspberry-pi-gpio egg. > > Maybe these modifications should simply be folded into the latter. > That

Re: [Chicken-users] another egg

> Great to learn that you are still around here and caring for the egg. > > If you like those changes, please pull them in. This would have the > advantage to reduce clutter/pollution of the eggs listing. > > Pls. notify the list. If you pull those changes in Mario should _not_ > include mine

[Chicken-users] New egg: punycode

Please can someone add this to the egg index? https://github.com/caolan/chicken-punycode Its used when working with internationalized domain names and converts domains in the style of "www.bücher.de" to "www.xn--bcher-kva.de" and vice-versa. If you're using domain names in your user-interface

Re: [Chicken-users] Starting up spiffy for dynamic content

Peter, for what it's worth I encountered exactly the same confusion when I first used spiffy (or rather, I arrived with the same preconceptions?). Perhaps this might be fixed by adding a clearly signposted example to the wiki which demonstrates the recommended way to implement this kind of dynamic

[Chicken-users] New egg: level-sexp

I've created a new module which allows you to read/write s-expressions to LevelDB. It's a 'level' implementation and works with the following eggs: * level * leveldb * sublevel The source can be found at: https://github.com/caolan/chicken-level-sexp Please can someone add this to the coop?

[Chicken-users] New egg: sodium

Please can someone add my new sodium egg to the coop? https://github.com/caolan/chicken-sodium.git It's a binding to the libsodium (https://libsodium.org) crypto library. The egg is a work in progress, but it already has a few useful procedures. Thanks, -- Caolan

Re: [Chicken-users] New egg: sodium

> I tested it here on my machine (x86-64, Debian 8, libsodium 1.0.0-1) and > got one test failure: > > (generic-hash (string->blob "")) . [ERROR] > > Error: crypto_generichash returned -1 > > Do you get this too? Ah yes, I forgot about this test case. Older

[Chicken-users] define-external and abort

I have been doing some work on the LMDB bindings (https://github.com/iraikov/chicken-lmdb) and submitted a patch for it's error-handling. Ivan and I are not 100% sure what I've done is safe, so I'd appreciate your expertise. Normally, I have my C bindings return an error code and then in scheme I

[Chicken-users] New egg: lmdb-lolevel

Please can someone add my new lmdb-lolevel egg to the coop: https://github.com/caolan/lmdb-lolevel I needed a few low-level things from the LMDB C API (like cursors and custom sort functions), so I've written a more low-level binding. I tried to follow the C API as closely as possible (without

Re: [Chicken-users] New egg LDIF

Jörg, I think you have a typo in the first line: (repo git "git://github.com/0-0-15/{egg-name}.git") Should that be 0-8-15 to match your username (instead of 0-0-15)? Caolan Jörg F. Wittenberger writes: > Hi, > > there's a new egg: > > Read/write LDIF,

[Chicken-users] New egg: gumbo

Please can someone add this to the egg index? https://github.com/caolan/chicken-gumbo It provides bindings to the Gumbo HTML parser from Google (https://github.com/google/gumbo-parser). I'm trying this out because html-parser and htmlprag don't support HTML5 input and I want something up and

CHICKEN 5 port of bencode egg

I recently merged a pull request from fancycade to port the bencode egg from CHICKEN 4 to CHICKEN 5. I've updated the release-info file and tagged a new release. https://github.com/caolan/chicken-bencode/ It's already been picked up by the CHICKEN 4 egg index, what else needs to happen for

Re: new egg: cmark

> Caolan: would you be ok for you if cmark for CHICKEN 5 points to > Harley's implementation? Yes, please go ahead - and thanks to Harley for creating a CHICKEN 5 version :) Caolan

Re: ldap-bind egg

Hi Sven, Vasilij, >> If so, is there a chance that it will be ported from Chicken-4 to Chicken-5? > > I've Cc'd the current maintainer of the egg. In case it's dormant, > porting and taking over its maintenance shouldn't be too hard due to the > low complexity of the code. I'm afraid I don't