From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 15:10:15 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC8924FA; Thu, 29 Nov 2012 15:10:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0CA878FC13; Thu, 29 Nov 2012 15:10:14 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA11964; Thu, 29 Nov 2012 17:10:13 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B77AD5.7030703@FreeBSD.org> Date: Thu, 29 Nov 2012 17:10:13 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Jonathan Anderson Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , David Wolfskill X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 15:10:16 -0000 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