Hi All, Not that I particularly support the addition of "substitutions" inside the current config parser, but one thing I have wanted myself is something similar to defines. Flipping the question to Saul, assuming we are all familiar with m4, what kind of parser additions would you need to completely omit m4 from your current configurations? This seems to be like an opportunity to brainstorm some new ideas, not only for 1.x branch, but possibly for 2.0 configuration files.
Thanks in advance, --Rudy Dynamic Packet Toll-Free: 888.929.VOIP ( 8647 ) On Fri, Mar 30, 2012 at 1:43 PM, Saúl Ibarra Corretgé <[email protected]> wrote: > Hi, > > On Mar 30, 2012, at 4:22 PM, Nick Altmann wrote: > >> I'm not agree with you, because I use m4 now. >> >> Such functionality was really useful together with include functionality. >> For example, when I have errors with m4 it's hard to understand in >> what line these errors occurred. >> >> m4 is not always convenient, >> I should compile my configuration every time, but I don't need all >> power of m4, I need only substitutions. >> m4 is not a panacea for all occasions. >> > > I agree with Vlad here. I maintain a huge configuration file consisting of > several m4 files and never felt the need to stretch the configuration file > syntax. > > > Regards, > > -- > Saúl Ibarra Corretgé > AG Projects > > > > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
