Mike Frysinger wrote: > On Monday 01 October 2007, Steve Long wrote: >> A place to start might be a list of all known variables from say the >> devmanual, along with whether they're allowed to be used as >> multi-parameters in `for' or function/cmd calls. So it's legitimate to >> see eg: for f in $A (even if it isn't space-proofed; that'd need an >> array.) > > i dont see how this is relevant, plus i dont really understand what you're > trying to say. this "multi-parameters" business just doesnt make sense.
Relevance is wrt automated checks for quoting, ie having a list of variables[1] like WORKDIR and T to check for quoting issues. Multi-parameter: according to devmanual, A is: "All the source files for the package (excluding those which are not available because of USE flags)." So it's a (presumably whitespace-separated) list of values, not just a singleton. Sorry if "multi-parameters" was a bad choice of word. [1] http://devmanual.gentoo.org/ebuild-writing/variables/index.html -- [EMAIL PROTECTED] mailing list
