El Martes, 29 de Diciembre de 2009, Jeremy Evans escribió: > On Dec 28, 4:37 pm, Iñaki Baz Castillo <[email protected]> wrote: > > El Martes, 29 de Diciembre de 2009, Jeremy Evans escribió: > > > You should also request the pg maintainer to maintain a versioning > > > scheme for pg that is outside of rubygems, similar to Sequel's > > > Sequel.version. Even though Sequel is distributed as a gem, Sequel > > > doesn't depend on rubygems, and therefore cannot use the rubygems API > > > to determined which pg gem is loaded. > > > > Isn't PGconn::VERSION (=> "0.8.0") valid? > > Not unless it was added after 0.8.0: > > $ irb -rubygems -rpg > irb(main):001:0> PGconn::VERSION > (irb):1: warning: toplevel constant VERSION referenced by > PGconn::VERSION > => "1.8.6" > irb(main):002:0> PGconn::VERSION() > NoMethodError: undefined method `VERSION' for PGconn:Class > from (irb):2 > > If it was added after 0.8.0, great.
Note that I uses the master version (or whatever it's called in mercurial). Inspecting that new code I see in ext/pg.c: static const char *VERSION = "0.8.0"; ... /* Library version */ rb_define_const( rb_cPGconn, "VERSION", rb_str_new2(VERSION) ); This is not present in gem version (0.8.0) so most probably it's a new adition and will be available for 0.9 :) Regards. -- Iñaki Baz Castillo <[email protected]> -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
