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