[IronPython] deriving IronPython

[ivan chollet]

For instance, people often would like to override methods such as
DumpStackTraces in PythonEngine or SuperConsole's methods, as well as
PythonCommandLine's methods.
IronPython's kernel is clearly not a request (unless someone would want to
rewrite it from scratch...), only the uppermost layers should ever be
concerned by overriding.
Methods such as PythonEngine.setStdout(...) are really helpful. That's the
kind of features we like, but it would be rather painful for you to develop
a comprehensive API with tons of such functions. Maybe being able to simply
override methods would be easier from the user's POV. I'm not fully
qualified to answer such questions but I thought that a simple user's
position could provide you with a different insight in IP's design issues.
Hope this helps!

Ivan chollet




-----Original Message-----
From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Dino Viehland
Sent: mardi 9 mai 2006 18:16
To: Discussion of IronPython
Subject: Re: [IronPython] deriving IronPython

Is there some specific functionality you'd like to override?  We certainly
wouldn't want to make all the methods virtual as it'd be a large backwards
compatibility burden, but we are actively looking at trying to improve these
APIs so whatever specific feedback you'd have hear would be great to hear=