[Gridflow-dev] feature requests: @fold1, @foldr, @foldr1,
@scan1. @scanr, @scanr1, unary ignore
Tom Schouten
doelie at zzz.kotnet.org
Wed Sep 8 20:55:03 EDT 2004
- Previous message: [Gridflow-dev] feature requests: @fold1, @foldr, @foldr1, @scan1.
@scanr, @scanr1, unary ignore
- Next message: [Gridflow-dev] feature requests: @fold1, @foldr, @foldr1, @scan1.
@scanr, @scanr1, unary ignore
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Wed, Sep 08, 2004 at 08:45:12PM -0400, Mathieu Bouchard wrote:
>
> On Wed, 8 Sep 2004, Tom Schouten wrote:
>
> > How do you see the idea of making pf support a compile time option of
> > gridflow? Libpdp is a system library independent of pd so this should
> > pose no problems.
>
> This is ok with me.
perfect.
> You just need to add a Feature.new {} block in
> ./configure. Maybe I should make a directory called optional/ for modules
> like this, because that doesn't belong in base/ for sure, and it doesn't
> belong in format/ because that dir is for [#in]/[#out] plugins.
>
yeah, by all means no hard dependencies. i'm not done breaking everything yet :)
maybe it's best i look at the list import/export objects as an example?
> > That is, as long it is possible to do this outside of gridflow core
> > with a pd object depending on both gridflow and libpdp, but i'm not
> > sure about this actually.
>
> GridFlow doesn't have a public interface yet. I don't think this will
> happen before 1.0 because I'm still changing a bunch of things. Actually I
> think that this will be the big feature of 1.0.
>
ok. so i do it internally. pf will probably change a bit before i
declare it stable 0.14 so it's easier to maintain that way.
- Previous message: [Gridflow-dev] feature requests: @fold1, @foldr, @foldr1, @scan1.
@scanr, @scanr1, unary ignore
- Next message: [Gridflow-dev] feature requests: @fold1, @foldr, @foldr1, @scan1.
@scanr, @scanr1, unary ignore
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Gridflow-dev
mailing list