Re: [OpenSIPS-Devel] [opensips] add width string transformation (#530)

2015-06-02 Thread Liviu Chircu
The **s.fill** transformations have been tuned a bit to also work exactly as the proposed **s.width**. Performance-wise, it will work exactly as **s.width** (memset if possible). Moreover, you can do left-alignment with spaces as well. --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] add width string transformation (#530)

2015-06-02 Thread Jarrod Baumann
Would it also be beneficial to have width as well, since it can also truncate longer strings to a specified width? --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/530#issuecomment-107917978___ Devel

Re: [OpenSIPS-Devel] [opensips] add width string transformation (#530)

2015-06-02 Thread Liviu Chircu
Merged #530. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/530#event-320008571___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] add width string transformation (#530)

2015-06-02 Thread Liviu Chircu
IMO, as long as they have decent applicability (i.e. pretty-logs for Call-IDs in this case), such transformations are nice additions. Also, **s.width** is shorter to write. --- Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] add width string transformation (#530)

2015-05-29 Thread Jarrod Baumann
this adds a string transformation primarily used for making pretty logs. for example: ``` xlog(L_INFO,$var(prefix): $(cs{s.width,7}): $(rm{s.width,9}): request from uac behind nat\n); ``` i looked into use `$(cs{s.fill.right, , 7})` but it wasn't meant for that it seems. You can view,