Hi,
It seems that the default behaviour of printing them to sys.stderr may fit our
needs.
Regards,
Markus
> -Ursprüngliche Nachricht-
> Von: users-boun...@lists.ironpython.com [mailto:users-
> boun...@lists.ironpython.com] Im Auftrag von Markus Schaber
> Gesendet: Montag, 4. April 2011 0
I'm working on writing C# libraries which can be imported by a variety
of .NET languages, DLR and otherwise, which appear native to the
language importing them.
For example, writing a C# function that can be used naturally in
IronPython as if it were written in Python, IronRuby as if it were
writt
Re: 1.
MutableString is convertible to String, so why would you need an object
parameter?
Tomas
-Original Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Doug Blank
Sent: Monday, April 04, 2011 8:25 AM
To: Discussion of IronPyt
On Mon, Apr 4, 2011 at 11:52 AM, Tomas Matousek
wrote:
> Re: 1.
>
> MutableString is convertible to String, so why would you need an object
> parameter?
Do you mean that one could write:
public static string expects_string(MutableString val) {
return (val as String);
}
I wrote:
Tomas means you can write this:
> public static string ExpectsString(string val) {
>return val;
> }
And call it from Ruby with a Ruby string:
expects_string "Foo"
~Jimmy
On Apr 4, 2011, at 12:21 PM, Doug Blank wrote:
> On Mon, Apr 4, 2011 at 11:52 AM, Tomas Matousek
> wrote:
>> Re
On Mon, Apr 4, 2011 at 12:54 PM, Jimmy Schementi wrote:
> Tomas means you can write this:
>
>> public static string ExpectsString(string val) {
>> return val;
>> }
>
>
> And call it from Ruby with a Ruby string:
>
> expects_string "Foo"
Yes, indeed, that works fine. Thanks! So, the DLR lan
For #3, you can avoid using an object argument and casting by typing the
argument as the the non-generic IList and IDictionary.
I think you're correct with #2 as F# doesn't support Nullable syntactically,
but it doesn't mean F# can't consume code using Nullable.
~Jimmy
On Apr 4, 2011, at 11:2
