[PD] save search path 0.43 OSX

Mathieu Bouchard matju at artengine.ca
Mon Feb 27 17:40:17 CET 2012

Le 2012-02-27 à 16:44:00, Roman Haefeli a écrit :
> On Sun, 2012-02-26 at 11:50 -0500, Mathieu Bouchard wrote:
>> Le 2012-02-26 à 11:50:00, Roman Haefeli a écrit :
>>> On Fri, 2012-02-24 at 15:16 -0500, Mathieu Bouchard wrote:
>>>> Le 2012-02-24 à 20:57:00, Roman Haefeli a écrit :
>>>>> In what way [import] shouldn't be used inside abstractions?
>>>> [import] is not very local, is it ?
>>> But it also works with multi-class externals. See my other mail.
>> But it's not very local, is it ?
> I got it (why are you repeating it?)

Because my point is that it doesn't import names of externals locally. So 
if it's not local, then it doesn't really matter that it does the same (?) 
with multi-class externals, because that's not what it should do.

Fortunately, nameclashes are a relatively rare occurrence, otherwise we'd 
more often hear things like « restart pd in order to avoid nameclashes 
caused by [import] being present in patches that have already been 
closed ».

> [zexy/dirac~] just simply doesn't work on a Debian box that has puredata 
> and pd-zexy installed. It seems that [zexy/dirac~] adds 'dirac~' to the 
> global namespace, not 'zexy/dirac~'. At least, when I create 
> [zexy/dirac~] in a patch in Pd-extended, I can create instances of 
> [dirac~] afterwards.

So, is this a bug in Zexy, or a bug in the way «namespacing» is 
implemented ? What does this case prove ?

| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC

More information about the Pd-list mailing list