Closed s3than closed 6 days ago
it could be conditionally generated for boolean types like this
if [ "$value" != "0" ]; then ... fi
instead of all that bc
and sed
stuff
This is also an optimisation (for bash code readability) issue as well
Compiler wise - I don't see any error. What's the problem here? It's not a bug. Am I missing something?
@Ph0enixKM Apologies .. I'll try and put together an example .. at one point I was seeing false come back as a not set value.. which was then triggering the error..
I'm not seeing that in the latest version.. I'm happy for this to be closed.
When creating a conditional on a boolean value the resulting bash returns the following
Boolean conditional
The resulting bash shows as
If the function was rewritten as follows
Same for true
Additionally the following would be good to have as an option
and
This only appears to affect Boolean checks