[sr-dev] [kamailio/kamailio] core: adding xavp_clone_level_nodata_with_new_name (#2070)

[Julien Chavanton]

<!-- Kamailio Pull Request Template -->

<!--
IMPORTANT:
  - for detailed contributing guidelines, read:
    https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
  - pull requests must be done to master branch, unless they are backports
    of fixes from master branch to a stable branch
  - backports to stable branches must be done with 'git cherry-pick -x ...'
  - code is contributed under BSD for core and main components (tm, sl, auth, tls)
  - code is contributed GPLv2 or a compatible license for the other components
  - GPL code is contributed with OpenSSL licensing exception
-->

#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)

#### Type Of Change

- [x] New feature (non-breaking change which adds new functionality)

#### Checklist:
- [x] Tested changes locally

#### Description
proposal for `xavp_copy()`
param1: source xavp name
param2: source xavp index
param3: destination xavp name

The command will copy only one specific xavp from the stack.
If the destination xavp stack exist it will append else it will create a new one, it seems to be more or less compatible to what we do with XAVP in general.

We can not reorder xavp stack like in the following example :

```
route[TEST] {
        $xavp(a=>x) = "a-0-x";
        $xavp(a[0]=>y) = "a-0-y";
        $xavp(a=>x) = "a-1-x";
        $xavp(a[0]=>y) = "a-1-y";
        xinfo("$$xavp(a[0]) = [$xavp(a[0]=>x)][$xavp(a[0]=>y)]\n");
        xinfo("$$xavp(a[1]) = [$xavp(a[1]=>x)][$xavp(a[1]=>y)]\n");

        $var(src_idx) = 1;
        $var(v) = "b";
        xavp_copy("a", "$var(src_idx)", "$var(v)");
        $var(src_idx) = 0;
        xavp_copy("a", "$var(src_idx)", "$var(v)");
        xinfo("$$xavp(b[0]) = [$xavp(b[0]=>x)][$xavp(b[0]=>y)]\n");
        xinfo("$$xavp(b[1]) = [$xavp(b[1]=>x)][$xavp(b[1]=>y)]\n");
}
```

```
 2(137) INFO: <script>: $xavp(a[0]) = [a-1-x][a-1-y]
 2(137) INFO: <script>: $xavp(a[1]) = [a-0-x][a-0-y]
 2(137) INFO: pv [pv.c:827]: w_xavp_copy(): xavp_copy(new): $xavp(a[1]) >> $xavp(b)
 2(137) INFO: pv [pv.c:833]: w_xavp_copy(): xavp_copy(append): $xavp(a[0]) >> $xavp(b)
 2(137) INFO: <script>: $xavp(b[0]) = [a-0-x][a-0-y]
 2(137) INFO: <script>: $xavp(b[1]) = [a-1-x][a-1-y]
```
You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/2070

-- Commit Summary --

  * core: adding xavp_clone_level_nodata_with_new_name

-- File Changes --

    M src/core/xavp.c (126)
    M src/core/xavp.h (14)

-- Patch Links --

https://github.com/kamailio/kamailio/pull/2070.patch
https://github.com/kamailio/kamailio/pull/2070.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2070
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20190920/30ca828b/attachment.html>