informational copy, was: serializing references [...]

ah zeev, did not knew that you didn´t follow, here is the final result we´ve got: SM>> The only way I see after thinking a bit on this is sort of LZW SM>> algorithm SM>> on variables. While serializing, keep serialized zval's in some SM>> list/hash, SM>> and if you see some zval twice, with is_ref set, you mark it as SM>> "referenced" in serialized data, pointing out which var it refers SM>> somehow SM>> (maybe just with running number). I'm not sure it is going to work SM>> in SM>> 100% of cases, needs much thinking about that. and further not to slow the others down that feature should by default be off able to follow? regards -- o----------0-¬---------O-·---¬----o---®-----o o O ° . | http://www.kiffen.de | pRoteçt y0ur bRaín |0 O ° ¤ ° · 0°·³°²'²³-¹'³´³°^°³~³²³°'³²²¨³²^³¹³²°²³`³º³°Þ ° o © ° . · | psychedelic experience | gott@kiffen.de | O ° o ° o-¬--o--0-----©-·--O-----o-----0-¤----------o 0 ° · ° . ¤ ·