Date: Thu, 29 Nov 2012 17:10:13 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Jonathan Anderson <jonathan@FreeBSD.org> Cc: FreeBSD Hackers <freebsd-hackers@FreeBSD.org>, David Wolfskill <david@catwhisker.org> Subject: Re: lib for working with graphs Message-ID: <50B77AD5.7030703@FreeBSD.org> In-Reply-To: <F74CCC1E80774094953032CFDAB8F12F@FreeBSD.org> References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> <F74CCC1E80774094953032CFDAB8F12F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/11/2012 17:02 Jonathan Anderson said the following: > On Wednesday, 28 November 2012 at 14:37, Andriy Gapon wrote: >> Graphs as in vertices, edges, etc :) And things like graph basics: BFS, DFS, >> connected components, topological sort, etc >> > > I've used igraph in my research: http://igraph.sourceforge.net/. It's very > full-featured, with attention to efficiency and sensible choices for (at least > some) algorithms, but it is GPL'ed rather than BSD-licenced. Yeah, a bummer for me. >> And, big oops sorry, forgot one very important detail - it has to be C. > > > > Does it have to *be* C, or does it have to be *interoperable with* C? For > instance, igraph has a core C library to do the heavy lifting, but I'd never > want to use it directly when exploring data sets because the Python wrapper API > is so very convenient (and I can pop the resulting data into matplotlib). It has to be C because I need to use it from C code in a "C runtime". -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B77AD5.7030703>