For backtraces to work correctly in interpreter mode, it is required that the
interpreter guard every call to C# code with a try-catch, so that the catch
block has a chance to stash away the backtrace if an exception is thrown. This
is done in Interpreter.InvokeMethod, and the catch block gives
Just FYI, MERLIN_ROOT will only be needed for a couple more weeks at most. I’m
almost finished with some internal repo changes that will allow the git
integration stuff to work. Once the git stuff works, we can get rid of all of
the SVN stuff, then MERLIN_ROOT won’t be a trigger.
JD
From: iron
Ah, I see; I misunderstood the way that flag was working.
-Original Message-
From: Shri Borde
Sent: Tuesday, December 30, 2008 1:23 PM
To: Curt Hagenlocher; IronRuby External Code Reviewers
Cc: ironruby-core@rubyforge.org
Subject: RE: Code Review: Thread#raise
The terminology I am using
The terminology I am using throughout is synchronous exception would be a
normal Kernel.raise as the thread knows exactly when and where the exception
will occur. Thread#raise is considered to raise an exception asynchronously as
you cannot control exactly when and where the exception will actua
Shouldn't the option "UseThreadAbortForSyncRaise" be called "...ForASyncRaise"?
I think that Thread.raise with no arguments should just inject a RuntimeError
with no message as if $! were nil; this makes more sense than failing. Trying
to reference a "current exception" in another thread is a sc
Are you using mono from macports?
Maybe it's better to build it from trunk
On Tue, Dec 30, 2008 at 5:58 PM, jirapong.na...@gmail.com <
jirapong.na...@gmail.com> wrote:
> try out but get another error.
> (in /Users/Jirapong/ironruby-jim/merlin/main/Languages/Ruby)
>
> ---
The error was my own fault.. just tried it again and it does work now.
On Tue, Dec 30, 2008 at 5:44 PM, Michael Letterle <
michael.lette...@gmail.com> wrote:
> What error did you get with my branch? It's currently building under Linux
> so I'm curious what the differences might be with OSX.
>
>
try out but get another error.
(in /Users/Jirapong/ironruby-jim/merlin/main/Languages/Ruby)
---
dlr_core
---
What error did you get with my branch? It's currently building under Linux
so I'm curious what the differences might be with OSX.
On Tue, Dec 30, 2008 at 8:27 AM, Ivan Porto Carrero wrote:
> Ok now that I know what that error message means i went ahead and forked
> ironruby also.
> I created a br
Ok now that I know what that error message means i went ahead and forked
ironruby also.
I created a branch called mono and it builds successfully on my mac with
mono.
I basically applied many of the fixes from seo's patch but for the git
layout and with the sources from 18/12/2008.
I think you al
2008/12/30 Ivan Porto Carrero :
> I've tried to build from source on OSX too.. with the latest trunk from mono
> but it won't compile I get the same error.
Try the latest patch on
http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/
(Or equivalently, Michael Letterle's git tree on github)
--
I've tried to build from source on OSX too.. with the latest trunk from mono
but it won't compile I get the same error.
to make the Rakefile work I had to make 2 minor changes.
In Rakefile I had to change the paths to the other rake files from \ to /
In rake/misc.rake I had to change line 107 to:
Yes, I install mono by MacPort. going to get mono source to try out.
Thank you,
-Jirapong
On Dec 30, 2008, at 1:19 PM, Michael Letterle wrote:
There are some bugs in mono 2.0 that will prevent you from compiling
IronRuby, your best bet is to use the SVN trunk, though I believe
2.2 works as
13 matches
Mail list logo
