Andreas Fink wrote:
depends on WHERE you do this macro
I often use it on ocstr_destroy by using O_DESTROY instead doing just
setting my octstr * to NULL after the call.
yep, as far as the octstr_create() is in the same stack scope.
If you pass the Octstr* pointer to several subsequent subcalls, and down the
lane you do gw_free(), then there is no use for it.
Complexity is the callstack IMO.
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
