#381: Losing track of a defined constant - possibly related to Module.autoload
---+
Reporter: kamal.fa...@… | Owner: lsansone...@…
Type: defect | Status: new
#373: protected methods aren't
-+--
Reporter: chr...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker |Milestone
Hi Laurent,
>> a very simple regular expression including a Japanese character
>> against a string contains same character doesn't match.
>>
>> It's very important issue for us, Japanese, and, I suppose, other
>> non-ASCII character languages.
>>
>> How about the status of supporting non-ASCII cha
You can now pass true Ruby objects to a table or outline view
datasource (since MacRuby doesn't use proxies) but keep in mind that
you must always pass the same unique references and not copies, as
mentioned in the documentation.
http://developer.apple.com/mac/library/documentation/Cocoa/Re
Hi Laurent:
In my RubyCocoa code I found that I had to create Obj C objects (using
alloc and an init call to super) to pass to NS tables since the UI
keeps copies of my objects. If all objects in MacRuby are Objective C
objects are the calls to alloc and to super still required?
Bob Rice
#382: undefined constants in Snow Leopard
+---
Reporter: r...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker | Mile
Hi Gp,
Yes there are several environmental issues when running RubySpec. For
example I noticed that it will fail if you have a /tmp/xxx directory
or if your $HOME is actually a symlink.
On Claudio's server I noticed a few more problems (you can see the
failures from the nightly build webs
Indeed, .xib is probably the way to go now. if one wants to submit a
patch for this I will merge it :)
Laurent
On Oct 12, 2009, at 9:04 AM, B. Ohr wrote:
Hi,
the XCode MacRuby templates are generating .nib files instead of xib
files (like Obj-C projects).
(.xib is better for diffs in gi
Hi Robert,
Could you be more explicit? I don't understand your question :)
Thanks,
Laurent
On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
Hi Team:
Converting a RubyCocoa project to MacRuby should I convert my
Objective C objects to normal Ruby objects (excluding NS objects)
and get rid
On Oct 12, 2009, at 1:50 AM, hiroshi saito wrote:
Laurent, thanks for fixing the bignum issue. OK I'll continue.
After updating to r2782, my rubyc successfully compiled all of stdlib,
and WOW!, all of build task completed! Thanks!
Nice :)
One of my intention of building MacRuby 0.5 trunk by h
I have been trying to run the specs and have found some weird issues
with some of the behaviour
spec/frozen/core/kernel/spawn_spec.rb - in the "Kernel uses the
current working directory as its working directory" it fails the test,
but if you change the command line to use MacRuby instead of
Hi,
the XCode MacRuby templates are generating .nib files instead of xib
files (like Obj-C projects).
(.xib is better for diffs in git or svn)
Bernd
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailm
Hi Team:
Converting a RubyCocoa project to MacRuby should I convert my
Objective C objects to normal Ruby objects (excluding NS objects) and
get rid of the call to alloc?
Bob Rice
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
Laurent, thanks for fixing the bignum issue. OK I'll continue.
After updating to r2782, my rubyc successfully compiled all of stdlib,
and WOW!, all of build task completed! Thanks!
One of my intention of building MacRuby 0.5 trunk by hand is checking
status of regular expression against non-ASCII
14 matches
Mail list logo
