#492: Need GCD Specs for Sources
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: major
#494: gsub with regexp is currently broken
-+--
Reporter: mattaimone...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#494: gsub with regexp is currently broken
-+--
Reporter: mattaimone...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
#477: Need GCD wrapper for dispatch_once
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: minor
Hi Brad,
Feel free to request MacRuby integration ideas to bugreporter:
http://bugreporter.apple.com/
The Xcode/Instruments/etc team will read them :)
Laurent
On Dec 8, 2009, at 7:08 PM, Brad Hutchins wrote:
Will MacRuby eventually be full integrated into Xcode. More exactly
I am wonderin
Will MacRuby eventually be full integrated into Xcode. More exactly I am
wondering about "Instruments" and other possible benchmarking tests to see
if its speed would be comparable (not exact as fast as straight ObjC) but in
the ball park. I know it will be used GCD, which I am very excited about
#492: Need GCD Specs for Sources
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: major
#434: MacRuby should use arc4random() rather than random()
---+
Reporter: j...@… | Owner: martinlagarde...@…
Type: defect | Status: new
Priority: blocker
#448: macirb fails to start on 32-bit arch (undefined method `bind' for
IRB::SLex:Class)
---+
Reporter: lo...@…| Owner: martinlagarde...@…
Type: defect | Status: new
#415: Crash with "Call result #2 has unhandled type" trying to display a window
---+
Reporter: trej...@… | Owner: martinlagarde...@…
Type: defect | Status: new
#493: signals cannot be intercepted
---+
Reporter: lsansone...@… | Owner: martinlagarde...@…
Type: defect | Status: new
Priority: blocker
#467: macrubyc generate binary that does not work using File.dirname
-+--
Reporter: jordan.breed...@…|Owner: lsansone...@…
Type: defect | Status: closed
#368: AOT compilation failing on this example
-+--
Reporter: mattaimone...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: major
#481: macrubyc doesn't let you use ruby's stdlibs
-+--
Reporter: mattaimone...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#368: AOT compilation failing on this example
-+--
Reporter: mattaimone...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major
#492: Need GCD Specs for Sources
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: major
#491: GCD Specs should block variable scoping/copying rules
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Prior
On Dec 8, 2009, at 4:01 AM, Giampiero De Ciantis wrote:
Frustrated, not upset. I never trust a system where the CI has been
red for this long.
RubySpec doesn't cover everything. I recommend that you build a
project and report us regressions. The "CI" system you refer to is
only meant to b
#490: GCD Specs for Semaphore class
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
#489: Need a top-level Dispatch Object
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: minor
#488: GCD Dispatch::Group#notify shouldn't expect any arguments
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
P
#488: GCD Dispatch::Group#notify shouldn't expect any arguments
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: defect | Status: new
P
#487: Enhanced GCD Spec for label and group
+---
Reporter: ernest.prabha...@… | Owner: lsansone...@…
Type: enhancement | Status: new
Priority: blocker
No problem , like Matt said, thanks for keeping us on our toes :)
I think the best way to do so is to have a goal. So pick a lib you
know you need:
* Run it in a sample or its test suite
* Wheep and moan in a corner ;)
* Grab coffee
* Pick a failure and lookup the specs of that functionality
*
Gp, thanks for keeping on our toes ;)
- Matt
On Tue, Dec 8, 2009 at 8:06 AM, Giampiero De Ciantis
wrote:
> Thanks Eloy. I'll take my panic pants off and get it at it again.
>
> I feel somewhat sheepish since I have been trolling through this code for
> months (I think a year now) and haven't bee
Great summary -- can someone validate and post on the MacRuby site, for future
reference?
Also, might be helpful to include links to the appropriates files so it is
easier to cross-check.
-- Ernie P.
On Dec 8, 2009, at 5:49 AM, ravenex wrote:
Just to make sure I got it right:
MacRuby's VM is
Thanks Eloy. I'll take my panic pants off and get it at it again.
I feel somewhat sheepish since I have been trolling through this code for
months (I think a year now) and haven't been able to submit a single patch. But
I will continue to try.
Cheers,
-Gp
On 2009-12-08, at 7:55 AM, Eloy Duran
@Ernie,
Thank you for the links. Actually I'm have read MRI 1.9's code
base before, so I was able to find quite a few "entry points"
that I needed to get up to speed with MacRuby. The problem is
I'm not familiar with the Objective-C runtime, and that's big
blocker for me, since MacRuby is tightly
Hi,
See my replies inline.
> Frustrated, not upset. I never trust a system where the CI has been red for
> this long.
>
> Here are the results I get, and they are fairly consistent. I don't know how
> you got the output you are showing, I am running "rake spec:ci" as described
> in the readm
Frustrated, not upset. I never trust a system where the CI has been red for
this long.
Here are the results I get, and they are fairly consistent. I don't know how
you got the output you are showing, I am running "rake spec:ci" as described in
the readme.
Gps-iMac:MacRuby Gp$ rake spec:ci
(in
30 matches
Mail list logo
