Hi Lenir,
unfortunately it cannot be done right now: first the script is parsed
via lex/yacc, but the validity of the function parameter is not checked;
the output is a execution tree; after that the the tree is used for
fixing the parameters of all functions; the error you get is generated
at this level, but here you do not have any info about positions in
script anymore....
regards,
bogdan
Lenir wrote:
Hey guys,
I would like to request a modification of the parser for AVPOPS. When
the parser finds a misconfiguration, it prints out something like this:
0(0) INFO:textops:hname_fixup: using hdr type name <Alert-Info>
0(0) ERROR:avops:fixup_pushto_avp: bad param 1; expected : $ru $du ...
ERROR: error -1 while trying to fix configuration
It would be nice if it printed the line where the error was found,
maybe something like:
0(0) INFO:textops:hname_fixup: using hdr type name <Alert-Info>
0(0) ERROR:avops:fixup_pushto_avp: bad param 1; expected : $ru $du
...on line: 300
ERROR: error -1 while trying to fix configuration
This would save a lot of time troubleshooting, specially those of us
who are migrating to the latest CVS versions of openser.
Thanks
Lenir
------------------------------------------------------------------------
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
