#346: Can't run macirb on Snow Leopard
+---
Reporter: comec...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: critical| Milesto
#346: Can't run macirb on Snow Leopard
+---
Reporter: comec...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: critical| Milesto
#346: Can't run macirb on Snow Leopard
+---
Reporter: comec...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: critical| Milesto
#346: Can't run macirb on Snow Leopard
+---
Reporter: comec...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: critical|Mile
#347: module in module_function mode can't have methods with default args
-+--
Reporter: mattaimone...@… | Owner: lsansone...@…
Type: defect | Status: new
I've installed a gem that I'm trying to use from the latest nightly; but
the embedded macruby runtime; does not find the gem.
Controller.rb:14:in `': no such file to load -- xml-object
(LoadError)
What do I need to do so that the embedded macruby can find my installed
gem?
I can perform the requi
Hi Laurent:
Thanks for your offer to help. Sorry I was busy with another project
but now I get back to MacRuby.
I have attached a file that causes the assertion error when loaded by
the require command. Probably there is something else I need to change
when porting from Ruby-Cocoa.
Than
Hi Robert,
The problem is line 68, the call to autorelease. If you remove it it
should load again. The reason is that autorelease (like release and
retain) are ignored selectors of the runtime. Clearly we should not
crash this way, I will fix that.
Also, keep in mind that retain, release
#347: module in module_function mode can't have methods with default args
-+--
Reporter: mattaimone...@… | Owner: lsansone...@…
Type: defect | Status: new
Hi Laurent:
Thanks for your quick reply. I have attached another file that causes
a similar crash without a call to autorelease.
Bob Rice
#
# OutlineRowNode.rb
# Cocoa-Ruby Driver Assistant
#
# Created by Robert Rice on 9/4/09.
# Copyright (c) 2009 Rice Audio. All rights reserved.
#
requ
Hi, is this the complete application? If not, could you generate subset of
your application that can be ran which produces the error message?
-Conrad
On Wed, Sep 23, 2009 at 2:46 PM, Robert Rice wrote:
> Hi Laurent:
>
> Thanks for your quick reply. I have attached another file that causes a
> s
Hi Robert,
The problem here is dealloc. Same reason, dealloc is ignored by the
runtime, and you should not use it in MacRuby, it will never be called.
I just fixed macruby to not crash in case autorelease or dealloc is
used, but keep in mind that using these selectors won't do anything.
L
Laurent, I understand that one should use the GC for MacRuby but why do we
have such a restriction? Just curious about the history here.
Thanks in advance,
-Conrad
On Wed, Sep 23, 2009 at 3:49 PM, Laurent Sansonetti
wrote:
> Hi Robert,
>
> The problem here is dealloc. Same reason, dealloc is ig
Hi Conrad,
The thing is, MacRuby is built on top of the ObjC GC, so there is
currently no way you can not use it :)
In the future we might introduce a mode where MacRuby doesn't use this
GC, but it's all tentative.
Laurent
On Sep 23, 2009, at 3:58 PM, Conrad Taylor wrote:
Laurent, I und
Hi Bob,
Did you embed MacRuby within your app? This could potentially explain
why it cannot find the gem.
Laurent
On Sep 23, 2009, at 12:05 PM, Stevenson, Bob wrote:
I've installed a gem that I'm trying to use from the latest nightly;
but the embedded macruby runtime; does not find the ge
So in that case Ruby would be garbage collected, but ObjC code it uses
will be ref counted?
Sent from my iPhone
On Sep 23, 2009, at 18:00, Laurent Sansonetti
wrote:
Hi Conrad,
The thing is, MacRuby is built on top of the ObjC GC, so there is
currently no way you can not use it :)
In
Hi, Objective-C could use GC and non-GC for memory management on the
desktop.
-Conrad
On Wed, Sep 23, 2009 at 4:51 PM, Jordan Breeding wrote:
> So in that case Ruby would be garbage collected, but ObjC code it uses will
> be ref counted?
>
> Sent from my iPhone
>
>
> On Sep 23, 2009, at 18:00, La
But would the new MacRuby interpreter be smart enough to switch
between them and prefer GC Objc-C code, or would it be locked to one
or the other?
Sent from my iPhone
On Sep 23, 2009, at 18:56, Conrad Taylor wrote:
Hi, Objective-C could use GC and non-GC for memory management on the
desk
In regards to a MacRuby application, you would need to use GC for
Objective-C.
-Conrad
On Wed, Sep 23, 2009 at 5:00 PM, Jordan Breeding wrote:
> But would the new MacRuby interpreter be smart enough to switch between
> them and prefer GC Objc-C code, or would it be locked to one or the other?
>
Hi Laurent:
Thanks again. This gets me past the compile crashes but now the
execution doesn't get very far before I get “EXC_BAD_INSTRUCTION” with
no backtrace. Any suggestions?
Program loaded.
run
[Switching to process 1521]
Running…
rb_main
requiring AppDelegate.rb
requiring DataBaseNew.r
Hi Robert,
This one will be hard to debug without your code. At least, from gdb,
could you do a "bt" and copy/paste the output?
Laurent
On Sep 23, 2009, at 5:17 PM, Robert Rice wrote:
Hi Laurent:
Thanks again. This gets me past the compile crashes but now the
execution doesn't get very
Hi again:
Does this help?
(gdb) bt
#0 0x7fff827521b2 in +[NSThread callStackSymbols] ()
#1 0x00010213700c in ?? ()
#2 0x000102132034 in ?? ()
#3 0x7fff81ab7408 in -[NSIBObjectData instantiateObject:] ()
#4 0x7fff81ab67f2 in -[NSIBObjectData
nibInstantiateWithOwner:topL
Very hard to tell, sorry. Contact me offline with a copy of your app
and I can investigate (if you don't want to share your source code
here).
Laurent
On Sep 23, 2009, at 5:57 PM, Robert Rice wrote:
Hi again:
Does this help?
(gdb) bt
#0 0x7fff827521b2 in +[NSThread callStackSymbols]
Sorry, I don't know if I missed something or not.
Currently MacRuby has a GC (as does Ruby) and it is based on Obj-C's
GC. This means that code pulled in to MacRuby MUST be GC currently.
In my opinion this isn't horrible or extremely difficult as you can
compile frameworks as -fobjc-gc inst
24 matches
Mail list logo
