Visibility of a method

By default methods within a class in Ruby is PUBLIC. But as we know, ruby supports meta programming and hence a new/updated code can be generated on fly during the runtime.
here is a way to make the public class methods to private.

class Myclass
  def mymethod
    puts "I am public and wishing to be private!"
  end
  private :mymethod
  # OR also can be written as
  # private_class_method :mymethod
end

obj = Myclass.new
obj.mymethod
# private method `mymethod' called for # (NoMethodError)

Similary public :mymethod or public_class_method :mymethod

Sorting an Array of hashes

We get a situation where we fetch some set of records from db as an array of hashes, and later we need to sort this array based on some field of DB.

Here is a very hand code to do so.

array_objs =[ {:title => "row1_title" ,:name => "Mumbai"},
              {:title => "row2_title" ,:name => "Delhi"},
              {:title => "row3_title" ,:name => "Bangalore"}  ]

array_objs .sort_by  {|array_objs|   array_objs [:name] }.each do |res|
  puts "#{res[:name] }"
end

O/P:
Bangalore
Delhi
Mumbai

Exception Handling in Ruby

>begin expression executes its body and returns the value of the last evaluated expression.
>Any error in begin part will be caught by rescue depending upon parameters
>ensure is the one which must be exectued irrespective of exception occured or not
>An error message caught by an exception can be accessed using $!

For Java Programmers [ begin => try ; rescue => catch; ensure => finally]

begin
 p "I am doing well"
 p "so well .. and well"
 a = 8/0
rescue
 p "Something went wrong => " + $!
ensure
 p "Oh Somehow I could finish my work"
end

O/P:

“I am doing well”
“so well .. and well”
“Something went wrong => divided by 0″
“Oh Somehow I could finish my work”

a = 8
b = 0
begin
 p "I am doing well"
 p "so well .. and well"
 if a==18
    p "I am happy with a as 8"
 elsif b == 0
    p "Lets say I dont want this"
    raise Exception
 else
    raise
 end

rescue
    p "Exception 1 caught here " + $!
rescue Exception
    p "Exception 2 caught here " +$!
ensure
 p "Oh Somehow I could finish my work"
end

O/P for [[ a = 8 and b = 0 ]]
“I am doing well”
“so well .. and well”
“Lets say I dont want this”
“Exception 2 caught here Exception”
“Oh Somehow I could finish my work”

O/P for [[ a = 8 and b = 1 ]]
“I am doing well”
“so well .. and well”
“Exception 1 caught here “
“Oh Somehow I could finish my work”

JRuby upgraded to version1.1

JRuby, which provides a version of the Ruby programming language to run on the Java Virtual Machine, has been upgraded, according to Sun.

Unveiled Monday as the second major project release, JRuby 1.1 features performance improvements, a re-factored IO implementation and improved memory consumption.

Also featured is compilation of Ruby to Java byte and an Oniguruma port to Java. Oniguruma is a regular expressions library.

“The main goal for version 1.1 was to improve performance,” said Sun engineer Thomas Enebo, in a statement released by Sun. “With the help from the community, we have made great strides in performance. There have been more and more reports of applications exceeding Ruby 1.8.6 performance; we are even beating Ruby 1.9 in some micro-benchmarks.”

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/

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.