<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2656.60"> <TITLE>RE : RE : [Nagios-users] Re: On-Demand Macros issue</TITLE> </HEAD> <BODY> Sorry but I don't understand what you mean when you say that 'every C preprocessor does it properly' ? You can arbitrarily decide to process macros inside out, but it means that a string like '$string1$string2$string3$' would be expanded as '($string1($string2$)string3$)', which is incompatible with the current way of expanding such a string. If I am wrong, please let me know because it would be a very nice feature to expand the variables recursively. > -----Original Message----- > From: Andreas Ericsson [<A HREF="mailto:ae@op5.se">mailto:ae@op5.se</A>] > Sent: Friday, May 27, 2005 10:49 AM > To: nagios-users@lists.sourceforge.net > Subject: Re: RE : [Nagios-users] Re: On-Demand Macros issue > > > François Laupretre wrote: > >>From: Bryan Loniewski [<A HREF="mailto:brylon@jla.rutgers.edu">mailto:brylon@jla.rutgers.edu</A>] > >> > >>Would others find this useful if a patch is applied? > >> > >> > >>> command_line $USER2$/foo $HOSTADDRESS:$ARG1$$ # Where > >>>$ARG1$=some_host_name > > > > > > Unfortunately, as the macro starting and ending tags are > the same ($), > > I think that you cannot implement such an extension in an > unambiguous > > way. > > Considering every C preprocessor does it properly, I'd say > it's not only > possible but also a fairly straightforward approach. Macros > just have to > be expanded inside out, instead of outside/none, and expanded > recursively. > > The biggest problem would probably be performance. > > > > Here is an example: > > > > If you get : > > > > $HOSTADDRESS:pre$ARG1$post$ > > > > If $ARG1$ is expanded prior to $HOSTADDRESS:therest$ this > wouldn't be a > problem. > > > It is impossible to choose between : > > > > ($HOSTADDRESS:pre$)ARG1($post$) > > And ($HOSTADDRESS:pre($ARG1$)post$) > > > > And it is still harder if you get something like > > '$HOSTADDRESS:pre$ARG1$ARG2$'. > > > > That would be '$HOSTADDRESS:pre$ARG1$$ARG2$$', as the > complete name of > each macro must be included (the last $ is to close the $ in > the beginning). > > > To conclude, unless you define some new tags for macro expansion, I > > think that this extension is not possible. And defining > some new tags > > would bring many compatibility problems. > > > > Bah. > > -- > Andreas Ericsson andreas.ericsson@op5.se > OP5 AB www.op5.se > Lead Developer > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps > using Yahoo! Search APIs Find out how you can build Yahoo! > directly into your own Applications - visit > <A HREF="http://developer.yahoo.net/?fr=offad-ysdn-" TARGET="_blank">http://developer.yahoo.net/?fr=offad-ysdn-</A>> ostg-q22005 > > _______________________________________________ > > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> > ::: Please include Nagios version, plugin version (-v) and OS > when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > </BODY> </HTML>