Re: [Ironruby-core] Incorrect library paths in App.Config

2009-02-13 Thread Ivan Porto Carrero
I think so.. I actually have an app.config.mine that I use to keep the paths correct. On Fri, Feb 13, 2009 at 3:13 PM, Pete Bacon Darwin bacondar...@googlemail.com wrote: Hi, I just noticed that the App.Config that is generated in an in Unsigned build of IronRuby (i.e. rake compile)

[Ironruby-core] revised package.rake

2009-02-13 Thread Ivan Porto Carrero
Hi, In my mono branch I use the following package task. It allows me to package up IronRuby and control the search paths. The problem with the previous task was that it shelled out to windows with windows specific commands. This made it fail on my mac of course. The code comes with no other

[Ironruby-core] Scratch that task.. some file paths have changed

2009-02-13 Thread Ivan Porto Carrero
That package task was what worked earlier this week. It looks like some of the paths have changed.. I'll fix it and update my repo. ___ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core

Re: [Ironruby-core] Throwing Exceptions defined in Ruby from C#

2009-02-13 Thread Shri Borde
I don't think your code below will work as multiple Ruby types share the same underlying CLR type. If you want to do things in a strongly-bound way, you would need to use the RubyUtils and other runtime helpers to find the method new, invoke it, etc. instead of using System.Reflection. An

Re: [Ironruby-core] Throwing Exceptions defined in Ruby from C#

2009-02-13 Thread Pete Bacon Darwin
Could you not achieve the wanted effect through a kind of monkey patching? I.E. Create the exception class in C# then redeclare it in the common.rb. The new class in Ruby would extend the one created in C# but wouldn't change anything if the C# one was there in the first place. If it was there,

Re: [Ironruby-core] Incorrect library paths in App.Config

2009-02-13 Thread Pete Bacon Darwin
Actually I guess that since all the paths are relative, the shouldn't need to be changed. I think I was assuming that mono users would automatically create their own App.config anyway, as a matter of course. Pete From: ironruby-core-boun...@rubyforge.org

Re: [Ironruby-core] Incorrect library paths in App.Config

2009-02-13 Thread Ivan Porto Carrero
This is from my app.config.mono set language=Ruby option=LibraryPaths value=../lib;../lib/ruby/site_ruby/1.8/;../lib/ruby/site_ruby/;../lib/ruby/1.8/ / On Fri, Feb 13, 2009 at 5:56 PM, Tomas Matousek tomas.matou...@microsoft.com wrote: Yep, you're right. Will fix App.config by the next

Re: [Ironruby-core] Throwing Exceptions defined in Ruby from C#

2009-02-13 Thread Daniele Alessandri
Yeah, I don't really like my solution exactly because it is dependent on the underlying type. By the way I already tried to call JSON::ParserError#new from C# to get an instance of the class and it actually worked, but then the exception was getting thrown with an empty stack trace (well I can

Re: [Ironruby-core] Throwing Exceptions defined in Ruby from C#

2009-02-13 Thread Daniele Alessandri
I will try going with this solution, thanks. As for the reusability of the code from other applications/languages, I think it would be something impossibile to begin with as the library is tightly coupled with ruby (especially the generator class, it interacts a lot with ruby code) and this is

Re: [Ironruby-core] Throwing Exceptions defined in Ruby from C#

2009-02-13 Thread Daniele Alessandri
I might try that just out of curiosity to see how it behaves, even though (honestly) I don't find it too much of a clean solution. Thanks! On Fri, Feb 13, 2009 at 19:57, Pete Bacon Darwin bacondar...@googlemail.com wrote: Could you not achieve the wanted effect through a kind of monkey

[Ironruby-core] $KCODE and encodings

2009-02-13 Thread Shri Borde
I was searching for string encoding issues in Ruby. Here is the summary of what I learnt, in case its useful to anyone else of if anyone has any corrections to this. Ruby 1.8 support for encoding: * A comment like # -*- coding: utf-8 -*- at the start of the file is supposed to

Re: [Ironruby-core] $KCODE and encodings

2009-02-13 Thread Matthew Wilson
On Fri, Feb 13, 2009 at 5:01 PM, Shri Borde shri.bo...@microsoft.comwrote: Ruby 1.8 support for encoding: ยท A comment like # -*- coding: utf-8 -*- at the start of the file is supposed to determine how to parse a .rb file, but I haven't really figured out how to make this work.

Re: [Ironruby-core] $KCODE and encodings

2009-02-13 Thread Shri Borde
If I use Notepad2's menu to set the encoding to UTF8 with signature, and run either ruby utf8_with_signature.rb or ruby -Ku utf8_with_signature.rb, the file fails to parse. The file is attached. If I save the file with encoding set just as UTF8, the file is 3 bytes smaller. ruby utf8.rb fails,

Re: [Ironruby-core] $KCODE and encodings

2009-02-13 Thread Tomas Matousek
AFAIK Ruby 1.8 doesn't support magic comments that specify encodings at all, 1.9 does. Ruby 1.8 also doesn't recognize BOM. Even version 1.9 has full encoding support, not just 2.0. Tomas From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri