# \-X:SaveAssemblies

**URL:** <https://www.ruby-forum.com/t/x-saveassemblies/147828>\
**Category:** IronRuby\
**Created:** [September 5, 2008, 8:02pm UTC](https://www.ruby-forum.com/t/x-saveassemblies/147828 "2008-09-05T20:02:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![KEKEKE](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/50afbb/32.png) [@KEKEKE](https://www.ruby-forum.com/u/KEKEKE)\
**Post date:** [September 5, 2008, 8:02pm UTC](https://www.ruby-forum.com/t/x-saveassemblies/147828/1 "2008-09-05T20:02:15Z")

</div>

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,