is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible?
-- juha
On 03/21/07 11:01, Juha Heinanen wrote:
is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible?
yes, still needs to be a integer. we can add to wishlist for next release to be able to give a PV.
Cheers, Daniel
-- juha
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Daniel-Constantin Mierla wrote:
On 03/21/07 11:01, Juha Heinanen wrote:
is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible?
yes, still needs to be a integer. we can add to wishlist for next release to be able to give a PV.
... or a string :-)
regards klaus
On Wed, 2007-03-21 at 16:33 +0100, Klaus Darilion wrote:
Daniel-Constantin Mierla wrote:
On 03/21/07 11:01, Juha Heinanen wrote:
is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible?
yes, still needs to be a integer. we can add to wishlist for next release to be able to give a PV.
... or a string :-)
I second this. Currently, I do use m4 macros to get that, but if I can do without it, the better :-) Besides, this feature looks particulary good in last SER versions config files :-)
regards klaus
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On 03/21/07 17:37, Jerome Martin wrote:
On Wed, 2007-03-21 at 16:33 +0100, Klaus Darilion wrote:
Daniel-Constantin Mierla wrote:
On 03/21/07 11:01, Juha Heinanen wrote:
is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible?
yes, still needs to be a integer. we can add to wishlist for next release to be able to give a PV.
... or a string :-)
I second this. Currently, I do use m4 macros
same I did, not feeling a strong demand for something else to route's parameter as I do m4 macros for many other values in the config. I was looking some time ago to embed m4 in openser, but couldn't get a C library for that. Is anybody aware of any m4 C library?
Cheers, Daniel
to get that, but if I can do without it, the better :-) Besides, this feature looks particulary good in last SER versions config files :-)
regards klaus
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
I second this. Currently, I do use m4 macros
same I did, not feeling a strong demand for something else to route's parameter as I do m4 macros for many other values in the config.
Don't get me wrong, having text labels in routes would not be enough for me to stop using m4, only not having to use it for THAT. :-)
I was looking some time ago to embed m4 in openser, but couldn't get a C library for that. Is anybody aware of any m4 C library?
Sorry, nope. I though that GNU m4 had a linkable C object compiled by default, but I did not double check that.
However, one issue I see there is the debugging complexity this adds : how do you know the line of a parse error ? You can know where it is located in the m4-preprocessed version; but never in the original m4 config file. This is one of the issues I see with using m4.
On 03/21/07 18:48, Jerome Martin wrote:
I second this. Currently, I do use m4 macros
same I did, not feeling a strong demand for something else to route's parameter as I do m4 macros for many other values in the config.
Don't get me wrong, having text labels in routes would not be enough for me to stop using m4, only not having to use it for THAT. :-)
knew that, just added my reason why adding string labels for routes was low priority.
I was looking some time ago to embed m4 in openser, but couldn't get a C library for that. Is anybody aware of any m4 C library?
Sorry, nope. I though that GNU m4 had a linkable C object compiled by default, but I did not double check that.
However, one issue I see there is the debugging complexity this adds : how do you know the line of a parse error ? You can know where it is located in the m4-preprocessed version; but never in the original m4 config file. This is one of the issues I see with using m4.
By separating the macros definition and m4 config files, you can use "divert" to purge the output of macros file, the result will be pretty much similar with m4 confi file.
Cheers, Daniel
By separating the macros definition and m4 config files, you can use "divert" to purge the output of macros file, the result will be pretty much similar with m4 confi file.
That is, you'll get the line numbers right if you use macros generating at most one line, but the column will still be wrong. In my case, I have really complex macros (mostly generating SQL queries, subsequent PV assignations, checking, etc.), and this does not work :-(
Jérôme Martin | LongPhone Responsable Architecture Réseau 122, rue la Boetie | 75008 Paris Tel : +33 (0)1 56 26 28 44 Fax : +33 (0)1 56 26 28 45 Mail : jmartin@longphone.fr Web : www.longphone.com
-
Daniel-Constantin Mierla -
Jerome Martin -
jh＠tutpro.com -
Klaus Darilion