the recent "Short Composition Challenge" teached me the existence of "ftgen"
but on the next page of the manual i found "ftgentmp"
this look safe to put inside instr-endin statements and the fact that
the table can be deleted at the end of the note activationthe sounds
attractive to me

so then:

i can put something radom generating to
iarga, iargb, ... -- function table arguments. Correspond to p5
through pn of the score f statement.
of
ifno ftgentmp ip1, ip2dummy, isize, igen, iarga, iargb, ...
so that the same orchestra can use random table everytime it makes a note?
hmm? but it is i-arg so .. it's not like that?
anyone using it that way?

at this moment .. am using the f-statement in the sco file
but this made algo-orc'n'sco creating with python a bit complicated
i mean taking control of numbers that inst and f-table use
ftgentmp seems to solve a lot .. and even gives me to make an orc flexible
is there any negative points of using ftgentmp(or ftgen) instead of
f-statement(in sco)?

tia

-- 
SaRiGaMa's Oil Vending Orchestra
is podcasting:
http://sarigama.namaste.jp/podcast/rss.xml
and supplying oil.py for free:
http://oilpy.blogspot.com/