30 Jan
2020
30 Jan
'20
8:56 p.m.
Hi,
I must have missed the discussion about it somewhere, but what is the
inspiration for the new $vn variable container?
According to the documentation, the only difference is that it can hold
$null values, whereas variables initialised in $var to $null are coerced
into an integer value of 0.
But why was this a concern? Why is it necessary? Is it not confusing to
users?
Thanks,
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
31 Jan
31 Jan
2:31 p.m.
Hello,
iirc, it was Alex Hermann that wanted to change $var(...) to be $null by
default and also hold $null as value.
But having it initialized (and reset) to 0 is very handy in many
situations, so I proposed to add a new variable. The need was the
ability to check if the variable was set or not, its value 0 might be
due to an assignment.
Cheers,
Daniel
On 30.01.20 18:56, Alex Balashov wrote:
Hi,
I must have missed the discussion about it somewhere, but what is the
inspiration for the new $vn variable container?
According to the documentation, the only difference is that it can hold
$null values, whereas variables initialised in $var to $null are coerced
into an integer value of 0.
But why was this a concern? Why is it necessary? Is it not confusing to
users?
Thanks,
-- Alex
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
1759
days inactive
1760
days old
1 comments
2 participants
participants (2)
-
Alex Balashov -
Daniel-Constantin Mierla