Hi Laurent,
(sorry for the longish post)
I did some simple tests where the bound variable is not actually bound to a
CoreData store, but to a method in the custom NSManagedObject class..
(btw - I am not sure if anyone else noticed but a difference between 0.4 and
0.5, is that when binding to c
#465: [0.5b2] Problem walking directory trees with unicode filenames
-+--
Reporter: robe...@…| Owner: lsansone...@…
Type: defect | Status: new
Priority:
#465: [0.5b2] Problem walking directory trees with unicode filenames
-+--
Reporter: robe...@…| Owner: lsansone...@…
Type: defect | Status: new
Priority:
Hey folks,
So, last time I brought this up, it seemed like there was an initial flurry of
interest and some volunteer participation, then *poof*. All that seemingly
went away. :)
Which is a shame because there have been some nice articles written about
MacRuby recently
(http://blog.nuclearsq
I'm not sure if this is a known bug, or related to any open issues with
bindings, but I found this while messing around (using r3059):
# This works
lv1 = 1
lv2 = 2
lv1_binding = lv1.send(:binding)
lv2_binding = lv2.send(:binding)
# This fails.
class A
lv1 = 1
lv2 = 2
lv1_binding = lv1.send(:bi
Hi Group:
The string.each method is undefined in MacRuby.
I can work around it by using string.each_byte then convert the fixnum back to
a character using the i.chr method.
Also string.split( "" ) does not convert the string to an array as it did
before.
Bob Rice
__
I think that String.each was mixed in from Enumerable, which 1.9 no longer does.
each is not a method on String in 1.9 either, so I don't think this is a
MacRuby problem.
You should file a bug for the problem with split().
On Nov 28, 2009, at 14:30, Robert Rice wrote:
> Hi Group:
>
> The stri
#424: performance regression from ruby 1.8 and 1.9
-+--
Reporter: jordan.breed...@…| Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
Hi Jordon:
each is a documented method for the the string class so it should be provided.
It is useful.
How would I go about filing a bug report?
Bob Rice
On Nov 28, 2009, at 3:35 PM, Jordan Breeding wrote:
> I think that String.each was mixed in from Enumerable, which 1.9 no longer
> does.
each is not documented for Ruby 1.9 that I know of, only for Ruby 1.8, do you
have the Pragmatic books? They don't like each as valid for String in 1.9.
If you need to file a bug though (especially for your split problem) try
https://www.macruby.org/trac/report
Jordan
On Nov 28, 2009, at 18:09
Also, just so you know this really is a 1.8 vs 1.9 problem and not an MRI vs.
MacRuby problem:
76 jor...@thetourist ~ > ruby test.rb
"hello, world!"
77 jor...@thetourist ~ > /opt/homebrew/bin/ruby test.rb
test.rb:3:in `': undefined method `each' for "hello, world!":String
(NoMethodError)
78 jor.
> each is a documented method for the the string class so it should be
> provided. It is useful.
As Jordan was saying String#each does not exist in 1.9 any more. And MacRuby
implements Ruby 1.9, so before saying something is a bug please check with 1.9.
By the way, 1.8's String#each is now the m
Hi, String#each is not supported in Ruby 1.9. Also, MacRuby is based
on Ruby 1.9 specification and not 1.8.
-Conrd
Sent from my iPhone
On Nov 28, 2009, at 4:20 PM, Jordan Breeding
wrote:
Also, just so you know this really is a 1.8 vs 1.9 problem and not
an MRI vs. MacRuby problem:
7
13 matches
Mail list logo
