chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] chunk-vector


From: Richard
Subject: Re: [Chicken-users] chunk-vector
Date: Sun, 5 Oct 2014 21:13:00 +0000

On Sun, 5 Oct 2014 20:52:26 +0200
Peter Bex <address@hidden> wrote:

> On Sun, Oct 05, 2014 at 08:12:59PM +0000, Richard wrote:
> > Hello all,
> > 
> > I have created a egg called 'chunk-vector' which is a
> > dyn-vector-like (http://wiki.call-cc.org/eggref/4/dyn-vector)
> > library capable of storing other srfi-4 vectors inside a dense
> > array.
> 
> Hi Richard,
> 
> Thanks!
> 
> > The stored vectors can be returned, changed and removed in O(1)
> > time.
> > 
> > This is, among other things, very handy when working with modern
> > OpenGL.
> > 
> > If it is not considered too specialised to be an offical egg; could
> > somebody upload it for me? (else, don't worry about it)
> 
> There are various much more specialised eggs in our coop, don't worry
> about that :)
> 
> > source:
> > https://github.com/pluizer/chunk-vector
> > release info
> > https://raw.githubusercontent.com/pluizer/chunk-vector/v0.1/chunk-vector.release-info
> 
> I've taken the liberty to add it as
> https://raw.github.com/pluizer/chunk-vector/master/chunk-vector.release-info
> instead.  The v0.1 link you posted would be forever unchanging,
> and presumably you'd like to be able to make new releases from
> master.
> 
> > documentation:
> > https://wiki.call-cc.org/eggref/4/chunk-vector
> 
> There are two small mistakes I noticed.  The first is that the
> procedure names are those of SRFI-4: f32vector-set! etc.
> It seems to me that should be f32chunk-vector-set! etc.
> 
> The other is a small typographical thing: /foo/ doesn't italicise
> the letters; our wiki uses the peculiar ''foo'' syntax for that.
> See https://wiki.call-cc.org/edit-help for more info about the exact
> syntax accepted by it.
> 
> Cheers,
> Peter

Hello Peter,

Thanks for adding my egg and spotting the mistakes in the
documentation. They have been fixed.

Dankjewel,
Richard



reply via email to

[Prev in Thread] Current Thread [Next in Thread]