On Fri, 2008-11-07 at 17:55 -0800, Miller Puckette wrote:
Actually, I think it would be a bad idea to have an abstraction affect the
search path of the containing patch. There would be no way for the patch to
know about the stuff getting added to the path until the abstraction gets
loaded...
On Wed, 2008-11-05 at 12:22 -0800, Miller Puckette wrote:
Followup: it looks like currently, declaring a path inside an
abstraction adds the declaration, buggily, to the whole line of parent
patches. one result of this is that, if you have a bunch of copies of
an abstraction declaring a
Hallo,
Miller Puckette hat gesagt: // Miller Puckette wrote:
I think (probably as you're saying below) that an abstraction's declarations
should affect only itself and things called from within it.
I think, that's what Luke meant, and I would agree here. Generally it's
not necessary and even
What's wrong with having a declare with a local scope? To have
functional namespaces that encourage encapsulation, there needs to be
at minimum two options: a global space and a completely local space.
Then other levels could be added as desired. Currently, there is a
global and a
On Wed, Nov 5, 2008 at 1:22 PM, Miller Puckette
[EMAIL PROTECTED] wrote:
Followup: it looks like currently, declaring a path inside an
abstraction adds the declaration, buggily, to the whole line of parent
patches. one result of this is that, if you have a bunch of copies of
an abstraction
With a little difficulty one could have it both ways by adding
something like a -exportpath flag -- an advantage for having
abstractions export paths to parents would be to have a master
abstraction with all the [declare]'s -- but more importantly it would
useful for looking for other resources
Hi Roman,
I think the -path and -stdpath aren't doing what I intended... I think
that if you've got a [foo] and [bar] with the same parent, then a declare
in [foo] shouldn't affect either the parent or [bar]. So if I can
figure out what's going wrong I'll try fixing that :)
thanks for checking
Followup: it looks like currently, declaring a path inside an
abstraction adds the declaration, buggily, to the whole line of parent
patches. one result of this is that, if you have a bunch of copies of
an abstraction declaring a path, it actually gets searched over and
over again every time a
hi all
i made some tests with the new [declare] in 0.42.0test5. here the
results:
-lib and -stdlib:
those expand the global namespace. when having [declare -stdlib
extra/zexy] somewhere, all zexy classes are available for any patches.
-path and -stdpath:
they expand the namespace of the parent
