Hi Daniel,
i will do that and backport the doc-update to the previous versions.
Bye Sven
** Am 24.02.2012 08:19, schrieb Daniel-Constantin Mierla:
On 2/22/12 10:26 AM, Sven Knoblich wrote:
Ah, ok. thanks. This explains the behaviour. But it isn't explicit
mentioned in the documentation what
On 2/22/12 10:26 AM, Sven Knoblich wrote:
Ah, ok. thanks. This explains the behaviour. But it isn't explicit
mentioned in the documentation what /g stands for.
But next time, i will also have a further look at the sources.
But now you can enhance the docs, just commit some more details there
Ah, ok. thanks. This explains the behaviour. But it isn't explicit
mentioned in the documentation what /g stands for.
But next time, i will also have a further look at the sources.
Bye Sven
Am 22.02.2012 09:26, schrieb Marius Zbihlei:
On 02/22/2012 09:45 AM, Sven Knoblich wrote:
Hello all,
On 02/22/2012 09:45 AM, Sven Knoblich wrote:
Hello all,
i am currently confused by using the avpops function avp_delete. When i
run avp_delete without the flag-value \g only the last value will be
unset (like an undo). Is this the wanted behaviour?
Hello Sven,
After looking thru the code it see
Sven,
It looks as if it's pushing onto avp stack. Try doing the assignment as
follows below.
$avp(test) := "value";
Sent from my iPhone
On Feb 21, 2012, at 11:45 PM, Sven Knoblich wrote:
> Hello all,
> i am currently confused by using the avpops function avp_delete. When i run
> avp_delet
Hello all,
i am currently confused by using the avpops function avp_delete. When i
run avp_delete without the flag-value \g only the last value will be
unset (like an undo). Is this the wanted behaviour?
EXAMPLE:
$avp(test) = "test"
if( $avp(test)){xlog("L_NOTICE","result1:$avp(test)\n");}
