#650: Issues with passing procs/methods to #map
+---
Reporter: pthom...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: major
Hi Jordan,
Yes please file a bug report, this looks like a nice enhancement.
Thanks,
Laurent
On May 5, 2010, at 1:30 PM, Jordan Breeding wrote:
> Right now for custom objects on the Objective-C side even if you provide a
> -[Object description] call to_s will fall through and hit to_s from NS
#685: inject doesn't work with Procs
-+--
Reporter: hghoe...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: major
#685: inject doesn't work with Procs
-+--
Reporter: hghoe...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major
#612: RegexpError: U_REGEX_BAD_ESCAPE_SEQUENCE
-+--
Reporter: cehoff...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#699: While installing twt, failed compile in yajl
-+--
Reporter: robe...@…| Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
#698: AddressBook framework doesn't load in TextMate
+---
Reporter: seanlilmat...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: minor
#698: AddressBook framework doesn't load in TextMate
+---
Reporter: seanlilmat...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: minor
#698: addressBook framework doesn't get load
+---
Reporter: seanlilmat...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: minor
Hi!
The problem might have been some Internationalization cache somewhere, which is
why I thought about rebooting.
Glad it fixed the problem :-).
As for loading framework Cocoa, 0.7 is not really that slower, it just depends
on which one you're calling first:
$> time macruby_select 0.5 -e 'fra
Hi,
thanks, after the reboot (not stupid!) the problem disappeared!
Very interesting, I didn’t expected that because 0.5 had no problems.
Maybe that happened because 0.7 is still slower than 0.5:
$ time macruby_select 0.7 -e 'framework "Cocoa“‘
real0m0.626s
user0m0.665s
sys 0m0.085s
#700: Escaped Unicode chars in hex are not recogized
+---
Reporter: jazz...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major | Miles
True. To a point but there is an overlap... Object String Hash etc.
Also designated initialisers are seldom used in ruby( preference for
named params). InitWithX:y:z is perhaps ok but init over initilize
seems odd.
Terry Moore
On 7/05/2010, at 9:25 PM, Matt Aimonetti
wrote:
In gener
In general it's just better and simple to follow Cocoa's conventions and
never overwrite the default initializer but instead create your own
initializer.
Thibault explained some of the reasons why you are running into some issues
but the point is that even though MacRuby is a Ruby implementation, y
I agree on that point of course they are different calls but from a ruby
point of view WHY isn't init with no args the same as initialize with no
args
So I can live with it but my preference is with ruby initialize... this is
macRuby right?
Terry
On 7/05/2010, at 6:09 PM, Thibault Ma
#699: While installing twt, failed compile in yajl
-+--
Reporter: robe...@…| Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
#698: addressBook framework doesn't get load
+---
Reporter: seanlilmat...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: minor
I have that in my TODO list, real life examples of things people might want
to do would be very appreciated tho.
- Matt
On Thu, May 6, 2010 at 9:20 PM, Paul Howson wrote:
> On 07/05/2010, at 1:08 PM, Matt Aimonetti wrote:
>
> > Duly noted ;)
>
> Actually Matt, could you perhaps consider a chapt
18 matches
Mail list logo
