Multiple definitions - templates & lists

[36.zZw_zRtW.910.32]

hehe

> I've got a few questions - tried to findem in the archive - no joy :(
> 
> 1. is there any simple way of avoiding "multiply defined" type errors when
> using arrays within an abstraction?  eg. can each instance of an abstraction
> in a patch, have its own copy of an array named say "fred"? 
> 
> or will I perhaps need to devise some tricky way of appending a unique id to
> the name, renaming fred "fred-id" - then letting the other objects in the
> abstraction know the new name of the array in case they need to access?

use it like this in an abstraction:
table $1
then have your superwindow say:
pd myjodelabstract blub

then it should be tabread blub and stuff except that you can conneckt
tabread (+ others) directly into the table obj, so you dont need a name
at all.
hm, see atach patch,although maybe, the $1 subpatch feature doesnt appear
to really work in 0.27 of pd? (shouldnt the table bear the name 'blub' in
this case?)
also , wasnt there an example in the docs for this once?
(abstractions.pd?) there's only subpatch.pd but it doesnt show this
feature ..


> 2. are there any patch examples or info available outlining the concept of
> "templates"?

doc/7.stuff/data-structures/*
and see the 0.intro.tyxt its not shown with the *.pd filterered open box
..


uzgul.xo
-------------- next part --------------
#N canvas 225 218 393 184 10;
#N canvas 0 15 394 227 myjodelabstract 0;
#X obj 234 102 table \$1;
#X obj 149 158 table;
#X msg 150 133 resize \$1;
#X floatatom 151 113;
#X msg 92 135 read \$1;
#X symbolatom 92 112;
#X msg 296 78 resize \$1;
#X floatatom 296 58;
#X msg 234 79 read \$1;
#X symbolatom 234 57;
#X connect 2 0 1 0;
#X connect 3 0 2 0;
#X connect 4 0 1 0;
#X connect 5 0 4 0;
#X connect 6 0 0 0;
#X connect 7 0 6 0;
#X connect 8 0 0 0;
#X connect 9 0 8 0;
#X restore 126 68 pd myjodelabstract blub;