Can somebody tell me how to call IronPython Interpreter with C# code,
so that I can embed Python into the .NET application.
Thank you!
___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cg
I think my objection to the pipe would be that it's a stretch to type, and has
visual conflict with I, 1, and l, depending on the display font. Perhaps
colon, rather than semicolon? I can still see conflict potential unless Guido
agrees to allow CPython to safely parse some new delimiters for
On Wed, Jul 20, 2005 at 11:14:13AM -0700, Keith J. Farmer wrote:
> I don't think it matters.. CPython doesn't understand List[int][0] =
> 1, anyway. We're purely within the .NET realm with this, I think.
Nope.
Using a semicolon would cause the expression to be syntactically
invalid, whereas usi
Title: Re: [IronPython] Plans for overloads?
Yes, we are in .NET realm, but we are still trying to find
solution that doesn't require change to the Python
syntax.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Keith J. FarmerSent: Wednesday, July 20, 2005 11:14
AMTo: Disc
I don't think it matters.. CPython doesn't understand List[int][0] = 1, anyway.
We're purely within the .NET realm with this, I think.
From: [EMAIL PROTECTED] on behalf of David Wilson
Sent: Tue 7/19/2005 7:21 PM
To: Discussion of IronPython
Subject: Re: [IronPy
On Tue, Jul 19, 2005 at 04:03:56PM -0700, Keith J. Farmer wrote:
> Perhaps ; instead of | ...
CPython couldn't parse that, so you couldn't write modules that worked
on both platforms that made use of FePy extensions.
David.
> From: [EMAIL PROTECTED] on behalf of Keith J. Farmer
> Sent: Tue 7/1
It'd have to be later tonight, if I remember. My 2k5 install's at home and
I've been spending my nights there learning how to use Exchange as a document
source for a website rewrite I'm doing.
Of course, I may take the night off for a personal James Doohan memorial movie
fest, instead.
Keith J. Farmer wrote:
Illustrating my concern with indexers:
delegate Foo DelegateType();
public static DelegateType this (Type type) { }
public Foo() { }
x = Foo[typeof(int)]() .. is ambiguous. You can't determine if you've
called the constructor, or if you've called the static indexer, pass
Keith J. Farmer wrote:
I didn't see a second set of square brackets. Also, what if what you
have is an indexer, in which case the parameter is supplied also with
square brackets?
Then you have a lot of square brackets? ;-)
Of course it's not very pretty. Do you have a suggestion that addres
Illustrating my concern with indexers:
delegate Foo DelegateType();
public static DelegateType this (Type type) { }
public Foo() { }
x = Foo[typeof(int)]() .. is ambiguous. You can't determine if you've
called the constructor, or if you've called the static indexer, passing
in the int type, and
I didn't see a second set of square brackets. Also, what if what you
have is an indexer, in which case the parameter is supplied also with
square brackets?
Of course it's not very pretty. Do you have a suggestion that addresses
my concern?
-Original Message-
From: [EMAIL PROTECTED]
[mai
11 matches
Mail list logo
