[IronPython] -X:SaveAssemblies

[KE]

Just to add, here are some problems with the pyc.py approach rather than
putting this logic into the DLR/DLR-implementor:

1. Worse performance since the file needs to be compiled and run
2. The pyc.py file itself is required to move around with the other
libraries when distributing a DLR-based runtime which needs to compile code

Thanks,

-----Original Message-----
From: KE [mailto:hellosticky at gmail.com] 
Sent: Friday, September 05, 2008 2:01 PM
To: IronPython; IronRuby (ironruby-core at rubyforge.org)
Subject: -X:SaveAssemblies

Hi,

I find it odd that the ConsoleOptions class only has a single FileName
string property. This forces the creation of pyc.py for creating a DLL with
one or more files to compile, whereas I believe the functionality in pyc.py
of creating a DLL from one or more input files should be right in the DLR.
OptionsParser even already has a switch for -X:SaveAssemblies.

IronRuby makes the same assumption. It adds the experimental -save option to
ir.exe, assuming only one input file (with the rest of the args being
arguments). I think it would be unfortunate if then IronRuby would need a
separate irc.rb to mimic pyc.py... rinse and repeat for every other
language.

Are people in agreement and this is just caused because ConsoleOptions
started off as executing one input file with args, and the issue of
compiling to a DLL was unforeseen? Is this planned to be changed? I would be
interested in changing this, so I don't mind doing the coding, but I don't
want to code something that is opposed on some unforeseen philosophical
basis.

Thanks,