Yep, the host resolves the source code & the engine type (this is in ScriptHost.ResolveSourceFileUnit which returns a ScriptSource (SourceUnit today) which is already bound to an engine). We haven't yet closely reviewed the ScriptHost API but I suspect it's pretty close to what it'll end up being.
Oh, I'm guessing Tomas moved the PublishModule onto ScriptEngine since Alpha 7, but it almost certainly does the same thing wherever it is :). Opening the bug sounds good - most likely this will just go away (as anything related to "modules" will), but we might end up reusing the code so it's good to have it tracked. Thanks! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Friday, January 04, 2008 3:36 PM To: Discussion of IronPython Subject: Re: [IronPython] Deleting a module from the host On Jan 4, 2008 3:26 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > > Then the ScriptRuntime would ask the > host to load the ScriptScope and depending on the host it'd search the web > server, the file system, the database, etc... for the appropriately named > file, and load it with the appropriate engine. So it would be the host that would both load the source and determine the engine, and the default Pythonic behavior (for the Python engine) would be available by using a "standard Python host"? > PublishModule (I suspect you mean it's on ScriptEngine) No, I'm using it on ScriptDomainManager.CurrentManager -- I don't see one implemented on ScriptEngine in the latest drop. There's a bug in ScriptDomainManager.GetPublishedModules that I've started running into; guess I'll post it to Codeplex. -- Curt Hagenlocher [EMAIL PROTECTED] _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
