love before being usable for real, and the guy stopped to develop it.
> Okay, mono.cecil is the answer, I would guess, I would look into it.
> On 10/11/07, Marcus Griep <neoeinst...@gmail.com > wrote:
> > The goal being that you can then write out a single assembly to file
> rather than requiring multiple assemblies. In memory, all within the same
> AppDomain, it doesn't make much difference. Part of that goal is to remove
> the dependance on Boo.Lang by embedding the used parts of it into the
> compiled application if requested, but externally, that would require
> ILMerge, and the license for it prohibits its redistribution.
> > On 10/10/07, Ayende Rahien <aye...@ayende.com > wrote:
> > > Why do you want that?
> > > Aside from doing stuff like internal, which is not something that I
> would greatly recommend.
> > > If you want to do that, Mono.Cecil can probably handle it
> > > On 10/11/07, Marcus Griep <neoeinst...@gmail.com > wrote:
> > > > Nicely done! Now if we can get in memory assembly merges (as in screw
> ILMerge), then we'd be more than set!
> > > > On 10/10/07, Ayende Rahien <aye...@ayende.com > wrote:
> > > > > More reasons to love Boo, I made it work, and I made it work nice:
> http://www.ayende.com/Blog/archive/2007/10/10/Multi-file-DSLs.aspx
> > > > > On 10/9/07, Marcus Griep <neoeinst...@gmail.com > wrote:
> > > > > > Ayende, check out "examples/pipeline/AutoImport ". There is a
> pipeline step written in there that attempts to compile and include imports
> that don't reference available assemblies. You may be able to modify it so
> that it adds the file as an input file during the compile. You can then
> specify the custom pipeline from the command line "/p:
> Rhino.Boo.AutoImport". It may be worth giving it a shot.
> > > > > > Marcus
> > > > > > On 10/9/07, Ayende Rahien <aye...@ayende.com > wrote:
> > > > > > > Yes, that is what I want.
> > > > > > > Although the idea is that this would simply instruct the
> compiler to also include this file as well, and they wouldn't get any
> special treatment otherwise.
> > > > > > > On 10/9/07, Marcus Griep <neoeinst...@gmail.com > wrote:
> > > > > > > > I think what Ayende is trying to do is pull it in as part of a
> script compile, bringing in "another.boo" without needing to explicitly name
> it in the compiler arguments, not just as part of an interpreted boo file.
> Myself, I'm not to sure about it as it "doesn't feel right"(tm) to me,
> though that doesn't mean it wouldn't be a useful feature. It would allow
> someone to create a master boo file that just includes references to all the
> files needed, and then have it all build just by using the master file on
> the command line. There are issues, though, with incorporating the file
> like that, such as how are namespaces handled, and are imports persisted to
> the included boo file.
> > > > > > > > Marcus
> > > > > > > > On 10/9/07, bull <bi_ill_...@yahoo.com > wrote:
> > > > > > > > > Just do : load("another.boo")
> > > > > > > > > In your case, you should rewrite the InteractiveIntepreter a
> bit so
> > > > > > > > > that it has a list of loaded scripts and never loads a
> script twice.
> > > > > > > > > That's quite easy
> > > > > > > > > On Oct 9, 4:58 am, "Ayende Rahien" < aye...@ayende.com>
> wrote:
> > > > > > > > > > Hi,
> > > > > > > > > > I assume that you are aware that I am using Boo for quite
> a bit of
> > > > > > > > > > scripting.
> > > > > > > > > > This means that something like: "import X from Foo" is
> extremely useful.
> > > > > > > > > > The problem is that occasionally I want to handle more
> than a single file.
> > > > > > > > > > Something like:
> > > > > > > > > > require "another.boo"
> > > > > > > > > > That would be understood by the compiler as an instruction
> to pull another
> > > > > > > > > > file as well.
> > > > > > > > > > Any comments about this?
> > > > > > > > > 覧
> > > > > > > > > Software Engineer
> > > > > > > > > Capabilities Development
> > > > > > > > > 781.652.6321
> > > > > > > > > VistaPrint
> > > > > > > > > Best Printing. Best Price.
> > > > > > > > > Business Cards are FREE at www.VistaPrint.com.
> > > > > > > > > 覧
> > > > > > > > > את.ψοｴ
> > > > > > > 781.652.6321
> > > > > > > VistaPrint
> > > > > > > Best Printing. Best Price.
> > > > > > > Business Cards are FREE at www.VistaPrint.com.
> > > > > > > 覧
> > > > > > > את.ψοｴ
> > > > > 781.652.6321
> > > > > VistaPrint
> > > > > Best Printing. Best Price.
> > > > > Business Cards are FREE at www.VistaPrint.com.
> > > > > 覧
> > > > > את.ψοｴ
> > > 781.652.6321
> > > VistaPrint
> > > Best Printing. Best Price.
> > > Business Cards are FREE at www.VistaPrint.com.
> > > 覧
> > > את.ψοｴ
|
