The UNIX and Linux Forums  


Go Back   The UNIX and Linux Forums > Top Forums > UNIX for Dummies Questions & Answers
.
grep unix.com with google



UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !!

Reply
English Japanese Spanish French German Portuguese Italian Powered by Powered by Google
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 11-27-2009
Registered User
 

Join Date: Nov 2009
Posts: 13
Test command - Two square brackets

Hello,
Can someone please explain to me the following line,
[[ -z $(echo $c | tr -d "\015") ]] && break

I do not understand why two test square brackets are used.

Thanks,
Shantanu

---------- Post updated at 03:38 PM ---------- Previous update was at 03:35 PM ----------

And, also why there's a $ before (echo $c | tr -d "\015")
Thanks,
Shantanu
  #2 (permalink)  
Old 11-27-2009
Registered User
 

Join Date: Oct 2009
Location: St. Louis, MO
Posts: 78
There may be other differences, but as far as I know [[ ... ]] is the same as [ ... ] except [[ ... ]] does not allow wildcard expansion.

The result of the command inside $( ) will be tested.
  #3 (permalink)  
Old 11-27-2009
Registered User
 

Join Date: Nov 2009
Posts: 13
Thanks Jsmithstl,
But, $ is used for variable subsitution. How is the use of $ in this expression related to that? Could you please explain more?

Thanks,
Shantanu
  #4 (permalink)  
Old 11-27-2009
chakrapani's Avatar
Registered User
 

Join Date: Sep 2009
Location: Asia
Posts: 87
[[ -z $(echo $c | tr -d "\015") ]] && break

The line means ..
echo $c
--> Just echo value of variable c

echo $c | tr -d "\015
--> value of variable c should if it contains special character "\015" it is something like line feed then delete it (Tr = translate )

$(echo $c | tr -d "\015")
---> Now this become a variable ... So suppose I say check if $VAR is good or I can put $(SOMETHING) then SOMETHING will be evaluated.


[[ -z $(echo $c | tr -d "\015") ]]
--> This is more like if [ SOME CONDITION ] then kind of ... shortcut .. Usually if people like to keep their job and dont want to loose to junior people ... Just kidding
--> So if you check what does -z mean from internet it says
-z = string is null, that is, has zero length
So What we have check if the result of evaluated variable is null or not ..

Now to the last part ..

[[ -z $(echo $c | tr -d "\015") ]] && break

--> && mean Anding .. Logical and .. or read in this case as THEN for if .. so it will break if condition in the if test is true ..
Now break is means break some loop and get out ... So this might be inside some loop ... Also you can have your own function here called ..

Added this
|| -> ORing if you want else part also ..

If you need more command to be excuted in then and also in OR ... you can write ..

[[ -z ... ]] && ( SOME COMMAND ) || ( SOME OTHER COMMANDS)


You can also write above as
VAR=$(echo $c | tr -d "\015")
if [ -z $VAR ];
then
break
fi

Please Note: all the above is true BASH scripting only ...
  #5 (permalink)  
Old 11-27-2009
radoulov's Avatar
--
 

Join Date: Jan 2007
Location: Варна, България / Milano, Italia
Posts: 3,074
Quote:
Originally Posted by Shan_u2005 View Post
Hello,
Can someone please explain to me the following line,
[[ -z $(echo $c | tr -d "\015") ]] && break

I do not understand why two test square brackets are used.

For most recent shells [ is a builtin command (it's a synonym for the "test" builtin).
Some shells like ksh93, zsh and bash support the shell keyword [[ which is supposed to be an enhanced version of the test command:
it supports a more friendly syntax for expressions with logical relations via the && and || operators, the variables inside are not subject to word splitting and pathname expansion (a.k.a. globbing) etc.

As far as the above example is concerned the command substitution $(command[s]) should be quoted if you use the test builtin command instead of the [[ ... ]] compound command.

Quote:
And, also why there's a $ before (echo $c | tr -d "\015")
$() is the newer supported by POSIX syntax for command substitution (the older one `...` is harder to read and less conducive to nesting).
  #6 (permalink)  
Old 11-27-2009
Registered User
 

Join Date: Nov 2009
Posts: 13
Thanks all
Shantanu
Sponsored Links
Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Double square brackets question King Nothing Shell Programming and Scripting 2 10-07-2009 05:40 PM
Use of double square brackets in ksh tsu3000 Shell Programming and Scripting 3 07-10-2009 03:37 PM
WHy the double square brackets? mojoman Shell Programming and Scripting 10 12-08-2008 01:54 PM
why put double square brackets in an if clause? napolayan UNIX for Dummies Questions & Answers 5 11-16-2006 03:18 AM
square brackets gilead29 UNIX for Dummies Questions & Answers 2 02-03-2004 11:29 AM



All times are GMT -4. The time now is 12:31 PM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0