Hello,
I am trying to call explicitly implemented interface method, but get
such error
undefined method `bar' for #
C# code:
public interface IFoo
{
void Bar();
}
public class Cls : IFoo
{
void IFoo.Bar() { }
}
Ruby code:
x = App::Cls.new
x.bar
Filed bug #23494.
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Alex 2k8
Sent: Thursday, January 08, 2009 2:25 AM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] Problem calling explicit interface met
Module#methods doesn’t return .NET members right now. It should. Filed a bug
#23493.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Wednesday, January 07, 2009 11:35 PM
To: ironruby-core@rubyforge.org
Subject: R
I'm not convinced this is exactly a bug. There is no public 'bar' method on
Cls after all. I think IronPython would require you to say something like
App::IFoo::bar(App::Cls.new()) in order to make the interface call explicit.
-Original Message-
From: ironruby-core-boun...@rubyforge.or
Could you sent source code for FarNet class (RegisterTool method declaration)?
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Alex 2k8
Sent: Wednesday, January 07, 2009 5:25 PM
To: ironruby-core@rubyforge.org
S
Fair enough, it could be called a feature :) There needs to be some way how to
call the method.
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Curt Hagenlocher
Sent: Thursday, January 08, 2009 8:05 AM
To: iron
Curious, how it is expected to work (or nobody thinked it over yet?)
Example to consider:
- - - -
public interface IFoo1
{
void Bar();
}
public interface IFoo2
{
void Bar();
}
public class Cls : IFoo1, IFoo2
{
void IFoo1.Bar() {}
> Could you sent source code for FarNet class (RegisterTool method
> declaration)?
http://code.google.com/p/farnet/source/browse/trunk/FarNet/FarNetIntf/Far.cs
http://code.google.com/p/farnet/source/browse/trunk/FarNet/FarNetPlugin/Far.h
http://code.google.com/p/farnet/source/browse/trunk/FarNet/
Btw, IronPython can call same method:
http://farnet.googlecode.com/files/IronPythonFar.1.0.35.rar
IronPythonFar\Scripts\calc.py
- - -
far.RegisterTool(ipy, "IronPython calculator", calc,
FarManager.ToolOptions.F11Menus)
- - -
--
Posted via http://www.ruby-forum.com/.
__
Not yet.
obj.as(IFoo1).Bar() might be one option.
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Alex 2k8
Sent: Thursday, January 08, 2009 8:54 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] P
Just to let people know where we are:
ruby core
1118 files, 4850 examples, 18036 expectations, 82 failures, 219 errors
1118 files, 4731 examples, 15341 expectations, 520 failures, 724 errors
14097/18063 = 78.0
ruby lang
47 files, 652 examples, 1725 expectations, 2 failures, 0 errors
ir
47 files
In IronPython, we went back and forth over this. On the one hand, the API
author might have chosen to make it harder to access the method, requiring a
cast like this:
App::Cls cls = new App::Cls();
cls.bar(); // syntax error
IFoo ifoo = (IFoo)cls;
ifoo.bar(); // works
OTOH, dynamic langua
What is the process for resolving a fixed bug? If I mark it as closed, Jim,
will you get a chance to verify that it is actually fixed and to ensure that
there is sufficient test coverage for the immediate issue as well as the larger
general area?
Thanks,
Shri
__
Just assign it to Jim. He'll mark it closed.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday, January 08, 2009 10:12 AM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] Resolving a bug on RubyForge
What
Don't close it. Just assign it to me, I'll verify and close it. It would be
nice to have a "Resolved" status, but I can't see a way to do it.
JD
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday, January 08, 2009 10:1
Hi,
I'm new to IronRuby. I'm trying to require a .net assembly but I have
the following error message. Any help will be very much appreciated.
Note :
--
MyApp.Application.dll references MyApp.Core.dll and both are in the same
folder C:\MyApp\Trunk\Bin\
Code :
--
require 'C:\MyApp\Tru
currently, you have to copy MyApp.Core.dll to the location where ir.exe is
located.
On Thu, Jan 8, 2009 at 1:46 PM, Sam Malone wrote:
> Hi,
>
> I'm new to IronRuby. I'm trying to require a .net assembly but I have
> the following error message. Any help will be very much appreciated.
>
> Note :
For me it works with a path too
http://code.google.com/p/ironruby-dbi/source/browse/trunk/src/ironruby-dbi/dbd-adonet/ADONET.rb
But I do use forward slashes
It does have some weirdness though, because sometimes I have to actually
copy the assembly to the directory where ir.exe lives. I'm not sur
Test Review:
classes.rb:
* can you change the get_status_... methods to status_... methods? The extra
get isn't really used in Ruby.
* Did you want to have possibly stale information in the Status class?
* for running thread, why not just do:
def status_of_running_thread
t = Thread.new {loop {}}
I meant that the status of the thread might change after you call Status.new,
however, it looks like you meant for that to happen:
" It should capture the state of the thread whenever Status.new was called."
I just wanted to be 100% sure this was the case. Everything else looks good.
JD
-
Inline..
Everything has been addressesd except I am not sure what you meant by " Did you
want to have possibly stale information in the Status class? ". The shelveset
has been updated.
Thanks,
Shri
-Original Message-
From: Jim Deville
Sent: Thursday, January 08, 2009 11:13 AM
To: iron
FYI. Going in as a direct commit.
tfpt review "/shelveset:rakefixes;REDMOND\jdeville"
Comment :
fixes some versioning and file ignores for Git integration
rakefixes.diff
Description: rakefixes.diff
___
Ironruby-core mailing list
Ironruby-core
Hello,
Ruby:
irb(main):001:0> foo = 3
=> 3
irb(main):002:0> foo
=> 3
IronRuby:
>>> foo = 3
=> 3
>>> foo
:0: undefined method `foo' for main:Object (NoMethodError)
Any idea, why this error thrown by IronRuby?
- Alex
--
Posted via http://www.ruby-forum.com/.
_
I'll be pushing it out tonight.
JD
-Original Message-
From: Tomas Matousek
Sent: January 08, 2009 5:28 PM
To: ironruby-core@rubyforge.org
Cc: Jim Deville
Subject: RE: [Ironruby-core] local variables: Ruby vs. IronRuby difference?
I fixed this a couple days ago. Don't know whether it
I fixed this a couple days ago. Don't know whether it has already been pushed
out. Jim?
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Alex 2k8
Sent: Thursday, January 08, 2009 4:53 PM
To: ironruby-core@rubyfo
Hello,
I get very odd results with attached code:
- - -
#
nil
#
- - -
While was expected
- - -
#
#
#
- - -
The 'nil' is printed by this expression:
form = form.test
and the test method definition is:
class Object
def test
p self
end
end
The hint: 'form' variable was set b
wait wait... Does this mean... we're getting LOCAL variables in the ir
REPL!?!?!?
On Thu, Jan 8, 2009 at 8:28 PM, Tomas Matousek wrote:
> I fixed this a couple days ago. Don't know whether it has already been
> pushed out. Jim?
>
> Tomas
>
> -Original Message-
> From: ironruby-core-b
y.e.s.
:)
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Michael Letterle
Sent: Thursday, January 08, 2009 10:26 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] local variables: Ruby vs. IronRuby difference?
wait wait... D
Yep. See also my blog post - http://blog.tomasm.net.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Michael Letterle
Sent: Thursday, January 08, 2009 10:26 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] local variables:
Another suggestion is to use name mangling to append "_of" to the method name.
This could return an object with a method called "do", "call", or something
like that. Since we already do name mangling from PascalCase to under_scores,
this could work out. It avoids having to pass the type paramete
30 matches
Mail list logo
