<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi,<br>
<br>
I'm bringing here a discussion started on devel list, as I would
like to get more opinions on the matter.<br>
<br>
The discussion started around the decision if makes sense to have
MACRO substitution (as text pre-processing) directly in OpenSIPS,
considering that right now M4 is heavenly used for this (as
additional tool to opensips).<br>
<br>
So, the debate was : have built-in text pre-processing <b>versus</b>
using M4 as text processor <br>
<br>
Pros for M4:<br>
- no effort to develop extra stuff - just install M4<br>
- can do really complex things (more than only macros, ifdef,
include, etc)<br>
- you can use it or not<br>
- easy to integrate with start / stop scripts<br>
Against for M4:<br>
- need to be installed and integrated<br>
- you may have a mismatch for the line number (if errors
reported in cfg) between the .m4 file and .cfg file<br>
<br>
Pros for buit-in:<br>
- you do no need to install M4 at all (everything comes
packet)<br>
- you may get accurate reporting on errors (for line in cfg) <br>
</tt><tt>Against for M4:<br>
- more devel work to re-implement macros, ifdef, etc<br>
<br>
<br>
Now, I would like to get your opinions on that (you as opensips
users), to see if we stick to using M4 for cfg pre-processing or
there is a real need to have this functionality as built-in.<br>
<br>
Thanks and regards,<br>
Bogdan<br>
</tt><tt><br>
</tt>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
</body>
</html>