[sr-dev] assigning $rd buggy?

[Daniel-Constantin Mierla]

Several notes in the context of the whole discussion:
- setting hostport and everything after @ are well defined operations 
specified internally but not exported to work as a variable -- should be 
easy to code, just needs a developer to do it :-)
- selects are still there as mentioned by Klaus, as separate framework. 
They can be accessed through PV framework as well, so @whatsoever is the 
same as $sel(whatsoever)
- transformations were intended to be chained in a simple way:

$(name{trans1}{trans2}...{transN}) - it is a valid syntax applying 
trans1 ... to transN to the value of variable $name. Besides that, they 
are working in xlog parameters, so you don't need to build the value of 
parameter before or do concat expressions as parameters. In other words, 
transformations are part of PV specification.

Cheers,
Daniel

On 7/4/11 3:22 PM, Martin Hoffmann wrote:
> Alex Balashov wrote:
>> On 07/04/2011 08:57 AM, Martin Hoffmann wrote:
>>
>>> Am I the only one who cringes at $(ru{s.select,0,:}) and a few other PV
>>> constructs?
>> On an aesthetic basis purely?
> Mostly. It is kinda hard to read and figure out. I know how all this came
> to be, but I'd really would have preferred a syntax like
> s.select($ru, 0, ':'), even though that still isn't very
> self-explaining.
>
>>> SER 2.x had this nice concept of hierarchic select. What happened
>>> to that?
>> For those coming from the OpenSER/Kamailio universe, can you elaborate
>> on how these worked?
> I was about to write a lengthy mail but, lucky for me:
>
>    http://sip-router.org/wiki/ref_manual/selects
>
> Regards,
> Martin
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda