Re: Scmutils in guile-2.0

2013-02-08 Thread Ludovic Courtès
Mikael Djurfeldt skribis: > On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès wrote: >>> +(cond-expand (guile-2 >>> + (define-syntax define-integrable >>> + (syntax-rules () >>> + ((_ form body ...) (define form body ...) >> >> You can actually use ‘define-

Re: Scmutils in guile-2.0

2013-02-08 Thread Mikael Djurfeldt
On Fri, Feb 8, 2013 at 10:54 AM, Ludovic Courtès wrote: > Mikael Djurfeldt skribis: > >> On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès wrote: +(cond-expand (guile-2 + (define-syntax define-integrable + (syntax-rules () + ((_ form body ..

Re: Scmutils in guile-2.0

2013-02-08 Thread Ludovic Courtès
Mikael Djurfeldt skribis: > On Fri, Feb 8, 2013 at 10:54 AM, Ludovic Courtès wrote: >> Mikael Djurfeldt skribis: >> >>> On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès wrote: > +(cond-expand (guile-2 > + (define-syntax define-integrable > + (syntax-rules () >

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Mark H Weaver
Nala Ginrut writes: > Here is a CSV reader based on Andy's csv-reader. > And it's ready for guildhall. [...] > PS: I'll call ijp to add it into the repo. I haven't yet looked carefully at this code or its API, so this is no judgement on you, but in general, I don't think we should follow the mode

Re: About Guile crypto support

2013-02-08 Thread Ludovic Courtès
Daniel Hartwig skribis: > On 5 February 2013 23:48, Ludovic Courtès wrote: >>> The gcrypt-guile project is doing so, I'll help it if I can. >>> But my original thought is orthogonal with gcrypt-guile, just put some >>> common digest algorithm in libguile rather than a full-stack crypto-lib. >> >

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Ludovic Courtès
Mark H Weaver skribis: > I haven't yet looked carefully at this code or its API, so this is no > judgement on you, but in general, I don't think we should follow the > model of "Hey, here's the first release of a library I just hacked up. > Please add it to Guildhall now." That's how we ended up

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Noah Lavine
This has been said before, but I think the most important thing is for people who are new to Guile to be able to see a list of "mature, well-maintained" libraries (whatever that means), and tell the difference between those and poorly-maintained or bitrotted libraries. It would also be nice to hav

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Aleix Conchillo Flaqué
On Fri, Feb 8, 2013 at 8:13 AM, Mark H Weaver wrote: > > I haven't yet looked carefully at this code or its API, so this is no > judgement on you, but in general, I don't think we should follow the > model of "Hey, here's the first release of a library I just hacked up. > Please add it to Guildhal

Re: splicing macros

2013-02-08 Thread Stefan Israelsson Tampe
Hi, Here is a git-format-patch of some docs for the ck macro. enjoy! On Sun, Jan 27, 2013 at 11:17 AM, Andy Wingo wrote: > On Sat 26 Jan 2013 14:03, Stefan Israelsson Tampe > writes: > >> I will assume that you are familliar with th ck macro, included in >> recent guile releases or else con

Re: About Guile crypto support

2013-02-08 Thread Daniel Hartwig
On 9 February 2013 00:21, Ludovic Courtès wrote: > > Yeah, apparently there are several half-baked bindings around. Let’s > just polish one of them, and submit it for inclusion in libgcrypt. I have already submitted some additions to one, but I may just continue in a new repository. By the way,

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Nala Ginrut
On Fri, 2013-02-08 at 11:13 -0500, Mark H Weaver wrote: > Nala Ginrut writes: > > Here is a CSV reader based on Andy's csv-reader. > > And it's ready for guildhall. > [...] > > PS: I'll call ijp to add it into the repo. > > I haven't yet looked carefully at this code or its API, so this is no > j

Re: [ANN] guile-csv 0.0.1 released!

2013-02-08 Thread Nala Ginrut
On Fri, 2013-02-08 at 08:59 -0800, Aleix Conchillo Flaqué wrote: > On Fri, Feb 8, 2013 at 8:13 AM, Mark H Weaver wrote: > > > > I haven't yet looked carefully at this code or its API, so this is no > > judgement on you, but in general, I don't think we should follow the > > model of "Hey, here's t