Archive for April 12th, 2008
RubyGems
A gem is a packaged Ruby application or library. It has a name and a version and have a specific task. Based on your requirement you may embed them into your application codes.
For eg.
activerecord 0.8.4
BlueCloth 0.0.4
captcha 1.1.2
cardinal 0.0.4
progressbar 0.0.3
rake 0.4.0
Gems are managed on your computer using the gem command. You can install, remove, and query gem packages using the gem command.
Installing RubyGems:
RubyGems is the name of the project that developed the gem packaging system and the gem command. You can get RubyGems from the RubyForge repository http://rubyforge.org/frs/?group_id=126
then type
ruby setup.rb
It installs the required library files and the gem command. This command gives us the power to do many things.
In a shortcut version at CLI we may use
q for query
r for remote
l for local
n for name
spec for specification
Listing remotely installable gems
gem query –remote
Searching remotely installable gems
gem query –remote –name-matches doom
# shortcut: gem q -R -n doom
Installing a remote gem
gem install –remote progressbar
or
gem ins -r progressbar-0.0.3
or
gem ins -r progressbar –version ‘> 0.0.1′
RubyGems allows you to have multiple versions of a library installed and choose in your code which version you wish to use.
Looking at an installed gem
gem specification progressbar
Listing all installed gems
gem query –local
remote or local
If you don’t specify either of these, then gem will (usually) try ’’both’’ a local and remote operation. For example:
gem ins rake # Attempt local installation; go remote if necessary
gem list -b ^C # List all local AND remote gems beginning with “C”
Coding With RubyGems
require ‘rubygems’
require ‘progressbar’
and then subsequently
bar = ProgressBar.new(“Example progress”, 50)
The first line of the program requires the progressbar library file. RubyGems will look for the progressbar.rb file in the standard library locations. If not found, it will look through its gem repository for a gem that contains progressbar.rb. If a gem is used, RubyGems attempts to use the latest installed version by default.
Specifying Versions
gem install –remote rake –version “0.4.14″
Updating RubyGems
gem update –system
or
gem install rubygems-update
update_rubygems
Uninstalling a gem
gem uninstall progressbar
Info extracted from : http://rubyforge.org/
Add comment April 12, 2008
and vs && in ruby
p true and false
p true && false
# true, false
p false and true
p false && true
# false, false
p true or false
p false or true
# true, false
p true || false
p false || true
# true, true
What happened???? You mean to say AND and && is different. In the same way OR and || behave in a distinct manner. No.
Still I don’t have a proper answer, except telling that here jack is with “p” or “puts” which always evaluates the very first parameter in case of “and” or “or”. When we use symbolic “&&” / “||” may be some precedence rule, which forces print statement to evaluate by having both operands left and right as well. means
p true && false ==> becomes ===> p (ture && false) , whereas
p true and false ==> becomes ===> p true //takes only one argument.
Please if someone has got a proper answer let me know.
2 comments April 12, 2008
