Hi Krzsysztof,
the thing about prepend brought me to a more general question about cyclone:
How do you deal with objects/features that are not optimally solved in MaxMSP and/or implemented differently in their (equally named) pd counterparts?
For example, the prepend object in Max/MSP can be sent a [set preatom( message, which then makes the object prepend "preatom" to every incoming message. Therefore you can't prepend to a message beginning with "set". In the iemlib2 this is solved in a way that the prepend object is static and can't be changed. In my prepend there's a second inlet to change the prepended atoms (and i cancel the [set preatom( feature for the future).
Therefore, the pd objects do not exactly mimic the Max behavior and patches are not fully portable.. and even worse.. differences may be hard to find.
greetings, Thomas