API Guidelines

From $1

No headers

Here are a couple pointers to follow when making a .NET API consumable by IronRuby:

Do not depend on .NET Attributes: IronRuby does not have a way to use them.
Do not depend on knowing a static type (related to #1): If you declare a class in IronRuby, the CLR class generated may be named something completely different, or may not be generated at all.
Avoid ambiguous overloads based on a params type: though this can be called by selecting the appropriate overload, normal Ruby method calls will not be able to select the proper overload.

Retrieved from "http://ironruby.net/Documentation/.NET/API_Guidelines"

Tags:

Attach file or image

Files (0)

Images (0)

Comments (2)

Viewing 2 of 2 comments: view all

mamadero says:

Some .NET Libraries rely on reflection (e.g. LINQ to SQL, Databinding, some IoCs. AFAIK we can't reflect on an IronRuby object from .NET. I think that should be mentioned as some of the points to consider.

Posted 14:05, 3 Aug 2009

Edit

Anonymous? says:

Thanks for giving us this information.

Posted 16:08, 19 May 2010

Viewing 2 of 2 comments: view all

You must login to post a comment.

API Guidelines

From $1

Table of contents

Table of contents

Recent pages

API Guidelines

From $1

Table of contents

Table of contents