Hi guys, I''ve just noticed that something happened to Thread.priority... It disappeared. I''m talking about Thread''s instance attribute - priority. I''m using the latest code from GitHub. The only available priority in the Thread instance now is a CamelCase priority, which is .Net''s Priority attribute... Take a look at the next REPL session: => #<Thread:0x000005e aborting>>>> t = Thread.new { puts "Start"; sleep(30); puts "end" }tart=> #<Thread:0x0000060 run>>>> t.priority:0: undefined method `priority'' for #<Thread:0x0000060 sleep> (NoMethodError)>>> t.Priority=> Normal I remember the priority attribute was problematic because it didn''t receive numeric values like MRI. Maybe this is related to that? Thanks, Shay. -- -------------------------------------------------- Shay Friedman Author of IronRuby Unleashed http://www.IronShay.com Follow me: http://twitter.com/ironshay
Ruby Thread#priority is not implemented yet. We disabled name mangling on built-ins recently so Thread.Priority property is not callable via lower-case name anymore. Tomas -----Original Message----- From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman Sent: Saturday, October 24, 2009 11:10 PM To: ironruby-core Subject: [Ironruby-core] Thread Priority Hi guys, I''ve just noticed that something happened to Thread.priority... It disappeared. I''m talking about Thread''s instance attribute - priority. I''m using the latest code from GitHub. The only available priority in the Thread instance now is a CamelCase priority, which is .Net''s Priority attribute... Take a look at the next REPL session: => #<Thread:0x000005e aborting>>>> t = Thread.new { puts "Start"; sleep(30); puts "end" }tart=> #<Thread:0x0000060 run>>>> t.priority:0: undefined method `priority'' for #<Thread:0x0000060 sleep> (NoMethodError)>>> t.Priority=> Normal I remember the priority attribute was problematic because it didn''t receive numeric values like MRI. Maybe this is related to that? Thanks, Shay. -- -------------------------------------------------- Shay Friedman Author of IronRuby Unleashed http://www.IronShay.com Follow me: http://twitter.com/ironshay _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
Is it going to be implemented for V1? If yes, is it going to work as MRI with numeric values? Thanks! Shay. On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote:> Ruby Thread#priority is not implemented yet. We disabled name mangling on > built-ins recently so Thread.Priority property is not callable via > lower-case name anymore. > > Tomas > > -----Original Message----- > From: ironruby-core-bounces at rubyforge.org > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman > Sent: Saturday, October 24, 2009 11:10 PM > To: ironruby-core > Subject: [Ironruby-core] Thread Priority > > Hi guys, > > I''ve just noticed that something happened to Thread.priority... It > disappeared. > I''m talking about Thread''s instance attribute - priority. I''m using the > latest code from GitHub. > > The only available priority in the Thread instance now is a CamelCase > priority, which is .Net''s Priority attribute... > > Take a look at the next REPL session: > => #<Thread:0x000005e aborting> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } > tart=> > #<Thread:0x0000060 run> >>>> t.priority > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> > (NoMethodError) > >>>> t.Priority > => Normal > > I remember the priority attribute was problematic because it didn''t receive > numeric values like MRI. Maybe this is related to that? > > Thanks, > Shay. > > -- > -------------------------------------------------- > Shay Friedman > Author of IronRuby Unleashed > http://www.IronShay.com > Follow me: http://twitter.com/ironshay > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >-- -------------------------------------------------- Shay Friedman Author of IronRuby Unleashed http://www.IronShay.com Follow me: http://twitter.com/ironshay
Hello, I have done a very basic implementation of a while back but I did not finish the modifications to the specs to test this. Here are the commits if you want to grab it http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 de7f305 http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b 164f202 It was decided at some point that there would only be 5 valid values -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities Lowest, BelowNormal, Normal, AboveNormal and Highest If anything lower than -2 is passed in the thread will be assigned Lowest and Highest if above 2. Pascal -----Original Message----- From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman Sent: October-25-09 3:55 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Thread Priority Is it going to be implemented for V1? If yes, is it going to work as MRI with numeric values? Thanks! Shay. On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote:> Ruby Thread#priority is not implemented yet. We disabled name mangling on > built-ins recently so Thread.Priority property is not callable via > lower-case name anymore. > > Tomas > > -----Original Message----- > From: ironruby-core-bounces at rubyforge.org > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman > Sent: Saturday, October 24, 2009 11:10 PM > To: ironruby-core > Subject: [Ironruby-core] Thread Priority > > Hi guys, > > I''ve just noticed that something happened to Thread.priority... It > disappeared. > I''m talking about Thread''s instance attribute - priority. I''m using the > latest code from GitHub. > > The only available priority in the Thread instance now is a CamelCase > priority, which is .Net''s Priority attribute... > > Take a look at the next REPL session: > => #<Thread:0x000005e aborting> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } > tart=> > #<Thread:0x0000060 run> >>>> t.priority > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> > (NoMethodError) > >>>> t.Priority > => Normal > > I remember the priority attribute was problematic because it didn''treceive> numeric values like MRI. Maybe this is related to that? > > Thanks, > Shay. > > -- > -------------------------------------------------- > Shay Friedman > Author of IronRuby Unleashed > http://www.IronShay.com > Follow me: http://twitter.com/ironshay > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >-- -------------------------------------------------- Shay Friedman Author of IronRuby Unleashed http://www.IronShay.com Follow me: http://twitter.com/ironshay _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
I remembered something like that. Thanks for pointing it out Pascal. Is it going to be incorporated into V1 code? Thanks! Shay. On Mon, Oct 26, 2009 at 1:49 AM, Pascal Normandin < pascal.normandin at convergentware.com> wrote:> Hello, > > I have done a very basic implementation of a while back but I did not > finish > the modifications to the specs to test this. > > Here are the commits if you want to grab it > > > http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 > de7f305 > > http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b > 164f202 > > It was decided at some point that there would only be 5 valid values > > -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities > Lowest, BelowNormal, Normal, AboveNormal and Highest > > If anything lower than -2 is passed in the thread will be assigned Lowest > and Highest if above 2. > > Pascal > > -----Original Message----- > From: ironruby-core-bounces at rubyforge.org > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman > Sent: October-25-09 3:55 PM > To: ironruby-core at rubyforge.org > Subject: Re: [Ironruby-core] Thread Priority > > Is it going to be implemented for V1? > If yes, is it going to work as MRI with numeric values? > > Thanks! > Shay. > > On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote: > > Ruby Thread#priority is not implemented yet. We disabled name mangling on > > built-ins recently so Thread.Priority property is not callable via > > lower-case name anymore. > > > > Tomas > > > > -----Original Message----- > > From: ironruby-core-bounces at rubyforge.org > > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman > > Sent: Saturday, October 24, 2009 11:10 PM > > To: ironruby-core > > Subject: [Ironruby-core] Thread Priority > > > > Hi guys, > > > > I''ve just noticed that something happened to Thread.priority... It > > disappeared. > > I''m talking about Thread''s instance attribute - priority. I''m using the > > latest code from GitHub. > > > > The only available priority in the Thread instance now is a CamelCase > > priority, which is .Net''s Priority attribute... > > > > Take a look at the next REPL session: > > => #<Thread:0x000005e aborting> > >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } > > tart=> > > #<Thread:0x0000060 run> > >>>> t.priority > > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> > > (NoMethodError) > > > >>>> t.Priority > > => Normal > > > > I remember the priority attribute was problematic because it didn''t > receive > > numeric values like MRI. Maybe this is related to that? > > > > Thanks, > > Shay. > > > > -- > > -------------------------------------------------- > > Shay Friedman > > Author of IronRuby Unleashed > > http://www.IronShay.com > > Follow me: http://twitter.com/ironshay > > _______________________________________________ > > Ironruby-core mailing list > > Ironruby-core at rubyforge.org > > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > > Ironruby-core mailing list > > Ironruby-core at rubyforge.org > > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > > -- > -------------------------------------------------- > Shay Friedman > Author of IronRuby Unleashed > http://www.IronShay.com > Follow me: http://twitter.com/ironshay > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >-- -------------------------------------------------- Shay Friedman Author of IronRuby Unleashed http://www.IronShay.com Follow me: http://twitter.com/ironshay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091026/f818812e/attachment.html>
Quick +1 to vote this patch up. I''ve been working on the JRuby support for the DataMapper ORM and DataObjects(.rb) database connectivity layer. These projects rely in turn on another project called Extlib, which provides a bunch of useful extensions (lazy arrays, thread pools, string extensions) for the other two projects. I pulled down and built the latest IronRuby and running Extlib''s specs, the lack of Thread#priority appears to be the first blocker in our support for IR. Alex Coles DataMapper: http://github.com/datamapper/dm-core DataObjects: http://github.com/datamapper/do Extlib: http://github.com/datamapper/extlib On Mon, Oct 26, 2009 at 6:12 AM, Shay Friedman <shay.friedman at gmail.com> wrote:> I remembered something like that. Thanks for pointing it out Pascal. > Is it going to be incorporated into V1 code? > Thanks! > Shay. > > On Mon, Oct 26, 2009 at 1:49 AM, Pascal Normandin > <pascal.normandin at convergentware.com> wrote: >> >> Hello, >> >> I have done a very basic implementation of a while back but I did not >> finish >> the modifications to the specs to test this. >> >> Here are the commits if you want to grab it >> >> >> http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 >> de7f305 >> >> http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b >> 164f202 >> >> It was decided at some point that there would only be 5 valid values >> >> -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities >> Lowest, BelowNormal, Normal, AboveNormal and Highest >> >> If anything lower than -2 is passed in the thread will be assigned Lowest >> and Highest if above 2. >> >> Pascal >> >> -----Original Message----- >> From: ironruby-core-bounces at rubyforge.org >> [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman >> Sent: October-25-09 3:55 PM >> To: ironruby-core at rubyforge.org >> Subject: Re: [Ironruby-core] Thread Priority >> >> Is it going to be implemented for V1? >> If yes, is it going to work as MRI with numeric values? >> >> Thanks! >> Shay. >> >> On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote: >> > Ruby Thread#priority is not implemented yet. We disabled name mangling >> > on >> > built-ins recently so Thread.Priority property is not callable via >> > lower-case name anymore. >> > >> > Tomas >> > >> > -----Original Message----- >> > From: ironruby-core-bounces at rubyforge.org >> > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman >> > Sent: Saturday, October 24, 2009 11:10 PM >> > To: ironruby-core >> > Subject: [Ironruby-core] Thread Priority >> > >> > Hi guys, >> > >> > I''ve just noticed that something happened to Thread.priority... It >> > disappeared. >> > I''m talking about Thread''s instance attribute - priority. I''m using the >> > latest code from GitHub. >> > >> > The only available priority in the Thread instance now is a CamelCase >> > priority, which is .Net''s Priority attribute... >> > >> > Take a look at the next REPL session: >> > => #<Thread:0x000005e aborting> >> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } >> > ?tart=> >> > #<Thread:0x0000060 run> >> >>>> t.priority >> > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> >> > (NoMethodError) >> > >> >>>> t.Priority >> > => Normal >> > >> > I remember the priority attribute was problematic because it didn''t >> receive >> > numeric values like MRI. Maybe this is related to that? >> > >> > Thanks, >> > Shay. >> > >> > -- >> > -------------------------------------------------- >> > Shay Friedman >> > Author of IronRuby Unleashed >> > http://www.IronShay.com >> > Follow me: http://twitter.com/ironshay >> > ________________________________________
What''s the status of the DataMapper port? I was just trying to use it but couldn''t get the gem installed. I''m interested in helping get this working. What next steps are needed? Thanks, Ryan Riley Email: ryan.riley at panesofglass.org LinkedIn: http://www.linkedin.com/in/ryanriley Blog: http://wizardsofsmart.net/ Twitter: @panesofglass Website: http://panesofglass.org/ On Mon, Oct 26, 2009 at 7:02 AM, Alexander Coles <alex at alexbcoles.com>wrote:> Quick +1 to vote this patch up. > > I''ve been working on the JRuby support for the DataMapper ORM and > DataObjects(.rb) database connectivity layer. These projects rely in > turn on another project called Extlib, which provides a bunch of > useful extensions (lazy arrays, thread pools, string extensions) for > the other two projects. > > I pulled down and built the latest IronRuby and running Extlib''s > specs, the lack of Thread#priority appears to be the first blocker in > our support for IR. > > Alex Coles > > DataMapper: http://github.com/datamapper/dm-core > DataObjects: http://github.com/datamapper/do > Extlib: http://github.com/datamapper/extlib > > > On Mon, Oct 26, 2009 at 6:12 AM, Shay Friedman <shay.friedman at gmail.com> > wrote: > > I remembered something like that. Thanks for pointing it out Pascal. > > Is it going to be incorporated into V1 code? > > Thanks! > > Shay. > > > > On Mon, Oct 26, 2009 at 1:49 AM, Pascal Normandin > > <pascal.normandin at convergentware.com> wrote: > >> > >> Hello, > >> > >> I have done a very basic implementation of a while back but I did not > >> finish > >> the modifications to the specs to test this. > >> > >> Here are the commits if you want to grab it > >> > >> > >> > http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 > >> de7f305 > >> > >> > http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b > >> 164f202 > >> > >> It was decided at some point that there would only be 5 valid values > >> > >> -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities > >> Lowest, BelowNormal, Normal, AboveNormal and Highest > >> > >> If anything lower than -2 is passed in the thread will be assigned > Lowest > >> and Highest if above 2. > >> > >> Pascal > >> > >> -----Original Message----- > >> From: ironruby-core-bounces at rubyforge.org > >> [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay Friedman > >> Sent: October-25-09 3:55 PM > >> To: ironruby-core at rubyforge.org > >> Subject: Re: [Ironruby-core] Thread Priority > >> > >> Is it going to be implemented for V1? > >> If yes, is it going to work as MRI with numeric values? > >> > >> Thanks! > >> Shay. > >> > >> On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote: > >> > Ruby Thread#priority is not implemented yet. We disabled name mangling > >> > on > >> > built-ins recently so Thread.Priority property is not callable via > >> > lower-case name anymore. > >> > > >> > Tomas > >> > > >> > -----Original Message----- > >> > From: ironruby-core-bounces at rubyforge.org > >> > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay > Friedman > >> > Sent: Saturday, October 24, 2009 11:10 PM > >> > To: ironruby-core > >> > Subject: [Ironruby-core] Thread Priority > >> > > >> > Hi guys, > >> > > >> > I''ve just noticed that something happened to Thread.priority... It > >> > disappeared. > >> > I''m talking about Thread''s instance attribute - priority. I''m using > the > >> > latest code from GitHub. > >> > > >> > The only available priority in the Thread instance now is a CamelCase > >> > priority, which is .Net''s Priority attribute... > >> > > >> > Take a look at the next REPL session: > >> > => #<Thread:0x000005e aborting> > >> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } > >> > tart=> > >> > #<Thread:0x0000060 run> > >> >>>> t.priority > >> > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> > >> > (NoMethodError) > >> > > >> >>>> t.Priority > >> > => Normal > >> > > >> > I remember the priority attribute was problematic because it didn''t > >> receive > >> > numeric values like MRI. Maybe this is related to that? > >> > > >> > Thanks, > >> > Shay. > >> > > >> > -- > >> > -------------------------------------------------- > >> > Shay Friedman > >> > Author of IronRuby Unleashed > >> > http://www.IronShay.com > >> > Follow me: http://twitter.com/ironshay > >> > ________________________________________ > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20100422/31267664/attachment-0001.html>
I''m working on installing datamapper from the sources. However, I have to manually execute `ir -S gem install .\pkg\_.gem` each time after the gem is created. I''m getting this error: C:\Users\ryan\dev\extlib>irake install ''irake'' is not recognized as an internal or external command, operable program or batch file. C:\Users\ryan\dev\extlib>ir -S rake install --trace (in C:/Users/ryan/dev/extlib) ** Invoke install (first_time) ** Invoke build (first_time) ** Invoke gemspec (first_time) ** Invoke gemspec:generate (first_time) ** Invoke version_required (first_time) ** Execute version_required ** Execute gemspec:generate Generated: extlib.gemspec ** Invoke gemspec:validate (first_time) ** Invoke version_required ** Execute gemspec:validate extlib.gemspec is valid. ** Execute gemspec ** Execute build WARNING: description and summary are identical Successfully built RubyGem Name: extlib Version: 0.9.15 File: extlib-0.9.15.gem ** Execute install Executing "ir install ./pkg/extlib-0.9.15.gem": ir install ./pkg/extlib-0.9.15.gem unknown: Could not find file ''C:\Users\ryan\dev\extlib\install''. (Errno::ENOENT) rake aborted! Command failed with status (1): [ir install ./pkg/extlib-0.9.15.gem...] C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:995:in `sh'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:1010:in `call'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:1010:in `sh'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:1091:in `sh'' C:/Users/ryan/.gem/ironruby/1.8/gems/jeweler-1.4.0/lib/jeweler/commands/install_gem.rb:15:in `run'' C:/Users/ryan/.gem/ironruby/1.8/gems/jeweler-1.4.0/lib/jeweler.rb:89:in `install_gem'' C:/Users/ryan/.gem/ironruby/1.8/gems/jeweler-1.4.0/lib/jeweler/tasks.rb:77:in `define'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'' C:/Program Files (x86)/IronRuby 1.0/lib/ruby/1.8/monitor.rb:242:in `mon_synchronize'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'' C:/Users/ryan/.gem/ironruby/1.8/gems/rake-0.8.7/bin/rake:31 C:/Users/ryan/.gem/ironruby/1.8/bin/rake:19:in `load'' C:/Users/ryan/.gem/ironruby/1.8/bin/rake:19 Shouldn''t this both build the gem and execute gem install on the created gem? Did I miss a step? Thanks! Ryan Riley Email: ryan.riley at panesofglass.org LinkedIn: http://www.linkedin.com/in/ryanriley Blog: http://wizardsofsmart.net/ Twitter: @panesofglass Website: http://panesofglass.org/ On Thu, Apr 22, 2010 at 9:51 PM, Ryan Riley <ryan.riley at panesofglass.org>wrote:> What''s the status of the DataMapper port? I was just trying to use it but > couldn''t get the gem installed. I''m interested in helping get this working. > What next steps are needed? > > Thanks, > > Ryan Riley > > Email: ryan.riley at panesofglass.org > LinkedIn: http://www.linkedin.com/in/ryanriley > Blog: http://wizardsofsmart.net/ > Twitter: @panesofglass > Website: http://panesofglass.org/ > > > > On Mon, Oct 26, 2009 at 7:02 AM, Alexander Coles <alex at alexbcoles.com>wrote: > >> Quick +1 to vote this patch up. >> >> I''ve been working on the JRuby support for the DataMapper ORM and >> DataObjects(.rb) database connectivity layer. These projects rely in >> turn on another project called Extlib, which provides a bunch of >> useful extensions (lazy arrays, thread pools, string extensions) for >> the other two projects. >> >> I pulled down and built the latest IronRuby and running Extlib''s >> specs, the lack of Thread#priority appears to be the first blocker in >> our support for IR. >> >> Alex Coles >> >> DataMapper: http://github.com/datamapper/dm-core >> DataObjects: http://github.com/datamapper/do >> Extlib: http://github.com/datamapper/extlib >> >> >> On Mon, Oct 26, 2009 at 6:12 AM, Shay Friedman <shay.friedman at gmail.com> >> wrote: >> > I remembered something like that. Thanks for pointing it out Pascal. >> > Is it going to be incorporated into V1 code? >> > Thanks! >> > Shay. >> > >> > On Mon, Oct 26, 2009 at 1:49 AM, Pascal Normandin >> > <pascal.normandin at convergentware.com> wrote: >> >> >> >> Hello, >> >> >> >> I have done a very basic implementation of a while back but I did not >> >> finish >> >> the modifications to the specs to test this. >> >> >> >> Here are the commits if you want to grab it >> >> >> >> >> >> >> http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 >> >> de7f305 >> >> >> >> >> http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b >> >> 164f202 >> >> >> >> It was decided at some point that there would only be 5 valid values >> >> >> >> -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities >> >> Lowest, BelowNormal, Normal, AboveNormal and Highest >> >> >> >> If anything lower than -2 is passed in the thread will be assigned >> Lowest >> >> and Highest if above 2. >> >> >> >> Pascal >> >> >> >> -----Original Message----- >> >> From: ironruby-core-bounces at rubyforge.org >> >> [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay >> Friedman >> >> Sent: October-25-09 3:55 PM >> >> To: ironruby-core at rubyforge.org >> >> Subject: Re: [Ironruby-core] Thread Priority >> >> >> >> Is it going to be implemented for V1? >> >> If yes, is it going to work as MRI with numeric values? >> >> >> >> Thanks! >> >> Shay. >> >> >> >> On 10/25/09, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote: >> >> > Ruby Thread#priority is not implemented yet. We disabled name >> mangling >> >> > on >> >> > built-ins recently so Thread.Priority property is not callable via >> >> > lower-case name anymore. >> >> > >> >> > Tomas >> >> > >> >> > -----Original Message----- >> >> > From: ironruby-core-bounces at rubyforge.org >> >> > [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shay >> Friedman >> >> > Sent: Saturday, October 24, 2009 11:10 PM >> >> > To: ironruby-core >> >> > Subject: [Ironruby-core] Thread Priority >> >> > >> >> > Hi guys, >> >> > >> >> > I''ve just noticed that something happened to Thread.priority... It >> >> > disappeared. >> >> > I''m talking about Thread''s instance attribute - priority. I''m using >> the >> >> > latest code from GitHub. >> >> > >> >> > The only available priority in the Thread instance now is a CamelCase >> >> > priority, which is .Net''s Priority attribute... >> >> > >> >> > Take a look at the next REPL session: >> >> > => #<Thread:0x000005e aborting> >> >> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } >> >> > tart=> >> >> > #<Thread:0x0000060 run> >> >> >>>> t.priority >> >> > :0: undefined method `priority'' for #<Thread:0x0000060 sleep> >> >> > (NoMethodError) >> >> > >> >> >>>> t.Priority >> >> > => Normal >> >> > >> >> > I remember the priority attribute was problematic because it didn''t >> >> receive >> >> > numeric values like MRI. Maybe this is related to that? >> >> > >> >> > Thanks, >> >> > Shay. >> >> > >> >> > -- >> >> > -------------------------------------------------- >> >> > Shay Friedman >> >> > Author of IronRuby Unleashed >> >> > http://www.IronShay.com >> >> > Follow me: http://twitter.com/ironshay >> >> > ________________________________________ >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core at rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20100422/ae62f45f/attachment.html>