I think you’re approaching this from a rather oblique angle, so to speak. According to ยง5.3.1/1: The unary * operator performs indirection: the expression to which it is applied shall be a pointer to an object type, or a pointer to a function type and the result is an lvalue referring to the object or … Read more
You’re looking for variable indirection, i.e. the ability to refer to a variable indirectly, by a name stored in another variable or returned from an expression. Note, however, that there are usually superior alternatives, such as using arrays or hashtables as multi-value containers – see this answer for an example. If you do need to … Read more
Generally it means that by increasing the level of abstraction one can make the problem easier to understand/resolve. Be careful with your abstractions though, the full quote at least as I heard it is, “You can solve every problem with another level of indirection, except for the problem of too many levels of indirection”.
Replace if (“state_$name” -eq “True”) { with: if ((Get-Variable -ValueOnly “state_$name”) -eq “True”) { That is, if your variable name is only known indirectly, via an expandable string, you cannot reference it directly (as you normally would with the $ sigil) – you need to obtain its value via Get-Variable, as shown above. However, as … Read more
arr$varEnvCol[$index]=”$(…)” doesn’t work the way you expect it to – you cannot assign to shell variables indirectly – via an expression that expands to the variable name – this way. Your attempted workaround with eval is also flawed – see below. tl;dr If you use bash 4.3 or above: declare -n targetArray=”arr$varEnvCol” targetArray[index]=$(echo $line | … Read more
First of all, your New-Variable invocation doesn’t do what you think it does, as you’d pipe the output of New-Variable to Where-Object instead of using the value of $Transactions | Where … as value for the variable. You need parentheses for that to work: New-Variable -Name “Transactions_$Year” -Value ($Transactions | Where {$_.Date -like “*.$Year” }) … Read more
http://dk.php.net/manual/en/function.constant.php echo constant($constant_name);
${!ARRAYNAME[@]} means “the indices of ARRAYNAME“. As stated in the bash man page since ARRAYNAME is set, but as a string, not an array, it returns 0. Here’s a solution using eval. #!/usr/bin/env bash ARRAYNAME=’FRUITS’ FRUITS=( APPLE BANANA ORANGE ) eval array=\( \${${ARRAYNAME}[@]} \) for fruit in “${array[@]}”; do echo ${fruit} done What you were … Read more
Context YAML version 1.2 user wishes to include variable placeholders in YAML have placeholders replaced with computed values, upon yaml.load be able to use placeholders for both YAML mapping keys and values Problem YAML does not natively support variable placeholders. Anchors and Aliases almost provide the desired functionality, but these do not work as variable … Read more
If you read the bash man page, it basically confirms what you have stated: If the first character of parameter is an exclamation point (!), a level of variable indirection is introduced. Bash uses the value of the variable formed from the rest of parameter as the name of the variable; this variable is then … Read more