From: "Ara.T.Howard" <Ara.T.Howard@...>
Date: 2005-10-12T23:41:45+09:00
Subject: ruby in the government - 1.6.x -> 1.8.x woes


one of the biggest stumbling blocks to the widespread adoption of ruby in my
lab is the fact what we've standardized on redhat enterprise for all of our
boxen.  it ships with 1.6.8.  this is a sorry state of affairs and i wonder
why it should be so.  the perl and python versions are resonable, thought not
cutting edge - any rational behind this?  anyone know how to go about changing
it?

on a related note - anyone know of a compatability layer to bridge 1.6.8 to
1.8.x for cgi libs specifically?  does the/a shim do this - the only one i have
doesn't seem too...  the cgi interface changed enough between 1.6.x and 1.8.x
to render useless any cgi code written for the former, for example:

   jib:~/eg/ruby > cat a.rb
   require 'cgi'
   cgi = CGI::new
   p cgi['k']

   jib:~/eg/ruby > echo k=v|ruby168 a.rb
   ["v"]

   jib:~/eg/ruby > echo k=v|ruby182 a.rb
   "v"

i can bridge it myself using

   class CGI
     alias_method '__idx__', '[]'
     def [] k
       [ __idx__(k) ].flatten.first
     end
   end

but then there is multipart form uploads/tempfile madness, etc. etc.  yuk.


regards.

-a
-- 
===============================================================================
| email :: ara [dot] t [dot] howard [at] noaa [dot] gov
| phone :: 303.497.6469
| Your life dwells amoung the causes of death
| Like a lamp standing in a strong breeze.  --Nagarjuna
===============================================================================