Si hay uno solo, se muestra la descripción del mismo.
Si son pocos, se muestra información resumida de cada uno.
However, be aware that because of the localisation issues explained above (if you skipped the previous Technical Note above then you might want to go back and read it or skip this section too), the variables might not actually be "local".
If the first element of the variable name already references a hash array then the variable update will affect the original variable.
Insignificant whitespace is ignored within directives so you can add variable definitions on the same line, the next line or split across several line with comments interspersed, if you prefer. The top-level variable namespace (hash) is copied, but no attempt is made to perform a deep-copy of other structures (hashes, arrays, objects, etc.) Therefore, a ) then you will change the original copy, regardless of any stash localisation.
Now we have a working replacement for Free BSD’s dead ports tree. Believe it or not: The latest code change was in April of 2014! Not a big problem, we can download those manually: # cd /usr/pkgsrc/07/distfiles # fetch # fetch # fetch Various dependencies will be downloaded, built and installed.
This can be useful when a variable is bound to a sub-routine or object method which you want to call but aren't interested in the value returned.
Variables may be assigned the values of other variables, unquoted numbers (2.718), literal text ('single quotes') or quoted text ("double quotes").
This behaviour can be a little unpredictable (and may well be improved upon in a future version).
If you know what you're doing with it and you're sure that the variables in question are defined (nor not) as you expect them to be, then you can rely on this feature to implement some powerful "global" data sharing techniques.