Ploki

I've read somewhere on this forum that sprintf takes MORE resources because... I forgot why.

Is it more economical to use combine where is feasible?

I've read somewhere on this forum that sprintf takes MORE resources because... I forgot why.
Is it more economical to use combine where is feasible?


combine-vs-sprintf

What do you mean by "profile your patch"?

I never knew that objects, thanks for pointing me to it.

The combine help file mentions: "Please note that for every single unique time that is output by combine a new symbol will be added to Max's symbol table consuming an ever growing amount of Max's resources."

In this behavior it is identical to sprintf. Was this what you are referring to? It means that in some cases it is better to avoid the use of sprintf or combine altogether.

@jvkr: yeah, that's what I was thinking about exactly.

@nicolas danet: Not exactly, because I'm dynamically accessing and writing directly to pattrstorage, so I need the form "patcher[x1]::sub patch[x2]::object "

I'm using join for actual to avoid having too many unique ID's for combine/sprintf objects.

I'll look into Shark as well, already using cpuclock.

@nicolas danet: Not exactly, because I'm dynamically accessing and writing directly to pattrstorage, so I need the form "patcher[x1]::sub patch[x2]::object "
I'm using join for actual  to avoid having too many unique ID's for combine/sprintf objects.

I'll look into Shark as well, already using cpuclock. 

So what's a way to concatenate without using up memory? Tosymbol?

combine VS sprintf?