#499: Order declaring class hierarchy gets MacRuby confused about instance
variables
--+-
Reporter: p...@…| Owner: lsansone...@…
Type: defect| Status: new
#499: Order declaring class hierarchy gets MacRuby confused about instance
variables
--+-
Reporter: p...@…| Owner: lsansone...@…
Type: defect| Status: new
Hi Jordan,
We are aware of this problem, but AFAIK we do not have a Trac bug for
it yet. Feel free to file a ticket :)
Laurent
On Dec 10, 2009, at 1:10 PM, Jordan Breeding wrote:
I was thinking that especially when testing the performance of a
pure ruby based class (Set) against a Cocoa c
#475: GCD Queues should print their label as their "to_s" method
+---
Reporter: ernest.prabha...@… |Owner: lsansone...@…
Type: enhancement | Status: closed
#475: GCD Queues should print their label as their "to_s" method
+---
Reporter: ernest.prabha...@… |Owner: lsansone...@…
Type: enhancement | Status: closed
#475: GCD Queues should print their label as their "to_s" method
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
#498: HACKING.rdoc uses "parentheses" when it means "braces"
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Prio
#495: Minor error in instructions for building LLVM
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: mi
Thanks!
On Dec 10, 2009, at 15:32, William Siegrist wrote:
> Sorry about the typo, it has been fixed.
>
> -Bill
>
> On Dec 10, 2009, at 1:03 PM, Jordan Breeding wrote:
>
>> Could we get the reply-to field on messages from
>> macruby-chan...@lists.macosforge.org changed from:
>>
>> macruby-.
Sorry about the typo, it has been fixed.
-Bill
On Dec 10, 2009, at 1:03 PM, Jordan Breeding wrote:
> Could we get the reply-to field on messages from
> macruby-chan...@lists.macosforge.org changed from:
>
> macruby-...@lists.macosforge.org
>
> to:
>
> macruby-devel@lists.macosforge.org
>
>
#487: Enhanced GCD Spec for Dispatch::Queue
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: minor
#487: Enhanced GCD Spec for Dispatch::Queue
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: minor
#487: Enhanced GCD Spec for Dispatch::Queue
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: blocker
#497: Enhanced GCD Spec for Dispatch::Group
+---
Reporter: ernest.prabha...@… | Owner: ernest.prabha...@…
Type: enhancement | Status: new
Priority:
I was thinking that especially when testing the performance of a pure ruby
based class (Set) against a Cocoa class (NSSet/NSMutableSet), it would be
useful to alias methods in the Cocoa side of things. My thought was then you
could have a single API to use in the rest of your code and you can ju
#490: GCD Specs for Semaphore class
+---
Reporter: ernest.prabha...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#492: Need GCD Specs for Sources
+---
Reporter: ernest.prabha...@… |Owner: lsansone...@…
Type: enhancement | Status: closed
Priority: major
Could we get the reply-to field on messages from
macruby-chan...@lists.macosforge.org changed from:
macruby-...@lists.macosforge.org
to:
macruby-devel@lists.macosforge.org
That way just hitting reply or reply to all should work to send a question
about a commit to the devel list?
On Dec 10,
#495: Minor error in instructions for building LLVM
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: mi
#496: spec/macruby/core/gcd_spec.rb should become a directory, one file per
class
+---
Reporter: ernest.prabha...@… |Owner: ernest.prabha...@…
Type: defect | Status
#496: spec/macruby/core/gcd_spec.rb should become a directory, one file per
class
+---
Reporter: ernest.prabha...@… | Owner: ernest.prabha...@…
Type: defect | Status:
#495: Minor error in instructions for building LLVM
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: mi
Sorry for the late reply.
> MacRuby's VM is called Roxor. Currently in the code in trunk doesn't use
> any interpreter mode; Ruby code is always compiled before is can be run.
Yes. There are plans to add a simple interpreter to be faster with simple
evals. It would interpret directly the Ruby pa
23 matches
Mail list logo
